transform_frames

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

With no annotations provided, the description carries full burden. It discloses that errors are returned as strings, ImportError is caught, and the epoch is optional. It does not explicitly state read-only nature, but the function is clearly a pure transformation.

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 front-loaded with a clear one-sentence purpose, followed by concise Args/Returns/Raises sections. No unnecessary words; every sentence adds value.

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?

Given the presence of an output schema (not shown but indicated), the description adequately covers purpose, parameters, and error handling. It could be improved by noting that this tool subsumes specific sibling converters, but overall it is complete.

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 coverage is 0%, so description compensates well. It explains coordinates as a dict with format dependent on frame, from/to frames as source/target, and epoch_utc as optional ISO format. This adds meaningful context beyond the schema's enums and generic object.

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 tool transforms coordinates between specific reference frames (ECEF, ECI, ITRF, GCRS, GEODETIC), using a specific verb (Transform) and resource (coordinates). It distinguishes from siblings like ecef_to_geodetic by covering all listed frames.

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 for coordinate transformation between any of the listed frames but does not explicitly differentiate from specific sibling converters (e.g., ecef_to_geodetic). No when-not-to-use or alternative recommendations are provided.

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