geodetic_wgs84_to_ecef_cartesian

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It states the conversion and the price (0.020 USDC on Base L2), which is useful context. However, it does not disclose whether both ECEF and ENU are always returned, whether the input is a JSON string with specific field names, whether height is required or defaults to 0, or any precision/unit details. The payment mention is a behavioral trait, but the core execution behavior is under-specified.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that front-loads the core conversion and adds the price as a secondary detail. It is compact and free of filler. The price parenthetical is arguably extra but relevant for cost-aware agents. No structural issues.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no output schema and no annotations, the description should explain what the agent will receive and any important input constraints. It does not describe the output format (e.g., whether it returns both ECEF and ENU, units in meters, or a JSON object). The payload parameter is a string, but the expected JSON structure is not described. Given the complexity of a geodetic conversion, this is a significant gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents both parameters. The description adds the coordinate frames (ECEF, ENU) and the input types (Latitude, Longitude, Ellipsoidal Height), which helps an agent understand what goes into the payload string. However, it doesn't specify the exact JSON structure or field names for the payload, so the agent must infer or inspect the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the conversion being performed: WGS84 geographic coordinates (Latitude, Longitude, Ellipsoidal Height) to ECEF and local ENU 3D vectors. It names the specific resource (geodetic coordinates) and the output frames. It doesn't explicitly distinguish from sibling tools like geospatial_geojson_to_3d_extrusion or calculate_bounding_box_3d, but the coordinate-system conversion is specific enough that an agent can infer its purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage: when you have WGS84 lat/lon/height and need ECEF or ENU vectors. It does not state when NOT to use it or name alternatives (e.g., geospatial_geojson_to_3d_extrusion for GeoJSON-based conversion, or calculate_bounding_box_3d for bounding boxes). No explicit exclusions or alternative routing, so it's adequate but not strong.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.