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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so the safety profile is covered. The description usefully adds cost (20 credits, Tier 2) and group metadata, but says nothing about output shape, latency, or whether ayanamsa/house-system choices affect results — a meaningful gap for a computational chart tool.

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?

Two short lines with the chart identity front-loaded and metadata bracketed. No filler, though the group/cost lines are administrative rather than task-guiding.

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?

For a 15-parameter, 4-required computational tool, the description gives only a name/domain and cost. Output schema existence excuses it from explaining return values, but it should still orient the agent on required birth data and the sidereal configuration parameters.

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 only 33%, so the description is obligated to compensate for the 15 parameters and does not: it mentions no parameter at all (date, time, latitude, longitude, ayanamsa, houseSystem, etc.). An agent gets no help choosing required inputs or sidereal defaults from the description.

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 chart type (Chaturvimsamsa/Siddhamsa) and its interpretive domain (education, learning, academic achievement), which distinguishes it semantically from sibling varga charts like D9 or D10. However, it never explicitly contrasts itself with the many neighboring varga tools, leaving sibling differentiation to 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?

No guidance on when to prefer this varga over the other 15 divisional charts or over astroway_specialized_vedic_divisional. The parenthetical domain hints at academic topics, but there are no exclusions, prerequisites, or named alternatives.

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