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

Annotations already declare readOnlyHint=false/openWorldHint=true/idempotentHint=false, and the description adds genuinely useful behavioral context: it is a POST endpoint, costs 250 credits (Tier 5), and is flagged heavy enough to require user confirmation. It does not cover auth or rate limits, but the cost/confirmation disclosure is real added value.

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?

Front-loads the core purpose in the first sentence, then inputs and output basis, with metadata lines clearly separated. Efficient with little waste, though the input listing is both inaccurate and space-consuming.

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?

Output schema exists, so return-value explanation is unnecessary, and the cost/heaviness warning is present. But the parameter-description mismatch leaves the agent unable to reliably map inputs, which is a meaningful completeness gap for an 8-param tool.

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 description lists inputs 'chart + transitDate (+optional transitTime/tzOffset), language, tone, length', but the schema exposes date, time, fields, ayanamsa, ayanamsaId, timezone, timezoneOffset, precision. Several named inputs (chart, language, tone, length) do not exist, and the actual compaction params (fields, precision, ayanamsa) are ignored — the description misleads rather than supplements the 63%-documented schema.

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?

States a specific verb+resource: 'Snapshot transit interpretation for a specific date' returning a narrative. The 'single date' scope implicitly distinguishes it from monthly/year-ahead narrative siblings, but no sibling is named explicitly, so differentiation relies on inference.

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?

Conveys when this applies (a single-date transit reading) and adds a critical 'confirm with user before invoking' warning tied to the 250-credit cost. However, it never explicitly contrasts against the many transit/report siblings (e.g. astroway_ai_interpret_transits, astroway_reports_transit_yearly), leaving alternative selection to inference.

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