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

With no annotations, the description carries the burden and does disclose the output structure in detail ('RETURNS: JSON with all Varshaphala sections: solar_return_chart, varshesha, muntha...'), making the result shape predictable. It omits prerequisites (birth data is mandatory), whether anything is persisted, and any performance/cost expectations, so it is good but not complete.

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 WHEN TO USE / WHAT IT DOES / RETURNS structure is front-loaded and scannable. The component list is partially repeated between the WHEN TO USE and WHAT IT DOES blocks, which is mild redundancy rather than waste.

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?

This is an 11-parameter tool with 5 required parameters and 0% schema coverage, and the description gives no guidance on supplying birth data, coordinates, timezone offset, or ayanamsa selection. The output schema exists, so explaining return values is optional, but the invocation side is materially under-specified for a tool of this complexity.

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 description coverage is 0% across 11 parameters, and the description adds no parameter-level meaning whatsoever — target_year, ayanamsa_mode, house_system, tz_offset, and the birth date/time fields are all left for the agent to infer. Only indirectly does 'annual prediction' hint at target_year's role.

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?

Names a specific verb and resource ('Calculate the full Varshaphala (annual prediction) report') and enumerates the pipeline components (solar return chart, Muntha, Varshesha, Mudda dasha, Sahams, Tajaka yogas, monthly outlook), which lets an agent distinguish it from narrower siblings like calculate_tajaka or calculate_vimsottari_dasha.

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?

The 'WHEN TO USE' block gives an explicit trigger condition: a comprehensive annual forecast for a person. It lacks any when-not guidance or named alternatives (e.g., use calculate_tajaka for only the Tajaka portion), so it falls short of a full 5.

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