Eclipse Path Map (SVG)

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

Description adds detail about rendering centerline and band, consistent with read-only annotations. Discloses map type (Equirectangular). No contradiction with annotations.

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 plus example, front-loaded with key information. Efficient but lacks comprehensiveness for parameter details.

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?

Tool has 5 parameters, nested options, no output schema. Description does not cover optional parameters, format options, or return structure. Incomplete for correct invocation without external knowledge.

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?

Zero schema description coverage for all parameters. Description provides an example using 'path', 'bandWidthDeg', and 'title' but does not explain 'centerlinePoints', 'options', or any nested fields. Very limited parameter meaning added.

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?

Clearly states it renders an eclipse path on an equirectangular world graticule, with centerline and shaded band. Distinguishes from siblings via specific rendering function.

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?

Grouped under Visualization but no explicit when-to-use or when-not-to-use compared to other render tools. Example shows basic usage but no guidance on alternatives.

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