Harmonic Chart

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

Description adds behavioral context beyond annotations: explains the calculation method (multiplying longitudes), valid harmonic range (H2–H36), and includes a group and cost. Annotations already indicate read-only, idempotent, non-destructive, so description reinforces safety while adding specifics.

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?

Three sentences: action, metadata, example. Efficiently structured with front-loaded purpose, no 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?

No output schema is provided, and the description does not explain what is returned (e.g., a chart object). The missing 'harmonic' parameter in the schema makes the tool incomplete as a callable function.

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 has 100% coverage but critically lacks the 'harmonic' parameter mentioned in the description and example. This creates a misleading expectation; the description implies a parameter that is not in the schema, making the tool effectively unusable as described.

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?

Description clearly states 'Calculate a harmonic chart by multiplying all planet longitudes by the given harmonic number (H2–H36)'. The verb 'calculate', resource 'harmonic chart', and method are all specified, distinguishing it from sibling chart tools.

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?

Description implies usage when a harmonic chart is needed, and provides an example request body. However, no explicit when-not or alternative tools are mentioned among the many specialized chart siblings.

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