Aspect Timeline

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

Annotations (readOnlyHint, destructiveHint, idempotentHint) already declare non-modifying behavior. The description adds that it calculates a timeline with enter/exact/leave dates and mentions cost (100 credits). This supplements the annotations without contradiction.

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 very concise: one sentence for purpose, plus group, cost, and example. No wasted words, and the key information is front-loaded.

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 7 parameters, no output schema, and 0% schema coverage, the description lacks detail on parameter formats and return structure. It mentions enter/exact/leave dates but not output fields. Users would struggle to use the tool correctly.

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% and description does not explain individual parameters. The example uses singular planet1Id, planet2Id, aspectAngle, orb, but the schema expects arrays (planet1Ids, planet2Ids, aspectAngles) and maxOrb. This mismatch is not clarified, causing confusion.

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 calculates a timeline of exact aspects between two planets within a date range, including enter/exact/leave dates. The verb 'calculate' and resource 'timeline' are specific, and it distinguishes from similar tools like 'aspects' or 'aspect_bar'.

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?

No explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites, when to prefer other tools, or exclusions. The example request body is provided but without usage context.

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