Transits Interpretation

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

Annotations (readOnlyHint, destructiveHint) are consistent with the read-only interpretation task. Description adds credit cost information. Missing detail about output format (AI-generated text) but overall adequate.

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 relatively short with front-loaded purpose statement. The example is lengthy and potentially misleading, but the overall structure is efficient.

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?

Inconsistencies between the example and schema leave gaps. No description of the return value (AI interpretation). For a complex nested-parameter tool, the description is insufficiently comprehensive.

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 descriptions cover 100% of parameters, but the example request body in the description uses keys 'windowStart' and 'windowEnd' that do not match the schema's required 'transitDate', causing confusion and reducing clarity.

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 verb 'interpretation' and resource 'transits to a natal chart', distinguishing it from natal-only interpretations. However, the phrase 'current/upcoming' and 'major transit' lack precise scope definition.

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 siblings like 'ai_explain_transit' or 'transits'. The group marker hints at category but does not specify selection criteria or exclusions.

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