transform_coords

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 usefully discloses the transformation basis (project origin and drawing scale) and that this is a pure coordinate conversion, but it never states that the call is side-effect-free, nor what shape the transformed value comes back in.

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?

A single tight sentence that front-loads the operation and the two spaces. Nothing is wasted, though it is arguably under-specified rather than deliberately minimal.

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?

With no output schema and no annotations, the description should at minimum indicate what is returned (a transformed point, presumably in the same x/y/z shape), which it omits. The 0% parameter coverage and nested input object also go uncompensated, so a caller still has open questions.

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 0% for two parameters, one of them a nested object with x/y/z, and the description adds no parameter-level meaning beyond the vague term 'coordinates' and 'local/world space'. It does not say how the optional z is treated, whether the direction enum is required, or what units apply.

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?

States a specific verb (transform) and resource (coordinates) plus the two spaces involved (local drawing space, world space), so the operation is unambiguous. It does not, however, differentiate itself from nearby siblings like reproject_point or reproject_points, which an agent could easily confuse with a coordinate transformation.

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?

There is no when-to-use guidance, no mention of prerequisites (e.g. that a project origin and drawing scale must already be set), and no routing to or away from alternatives such as reproject_point. The reader must infer all usage context.

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