export_takeoff

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

With no annotations provided, the description details the coordinate system, units, and payload contents. It implies a read-only operation (no destructive hint needed) and mentions the optional disk write side effect. No contradictions.

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?

Two sentences convey the purpose, usage, and key coordinate details. Every sentence provides necessary information with no redundancy or wasted words.

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 no output schema, the description adequately explains the return format (inline JSON) and the coordinate system. It covers the essential aspects for an export tool, though it could mention any limitations on payload size.

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?

The schema covers the 'path' parameter 100%, but the description adds critical context: without 'path', the payload is returned inline; with it, it is written to disk as JSON. This goes beyond the schema's simple description.

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 identifies the tool as exporting the full annotations payload that the app autosaves and can import. It specifies the payload format and distinguishes from sibling tools by focusing on export rather than editing or measurement.

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 explains that the output is returned inline and that providing a path writes to disk. It gives clear guidance on the optional parameter, though it does not explicitly discuss when not to use this tool versus alternatives.

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