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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds beyond that by explaining the computational purpose (calculate declinations, find parallels/contraparallels) and the nature of the output (declination per planet, all aspects). No contradictions; the keyword stuffing at the end is minor noise.

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 three sentences plus a trailing keyword phrase ('Declination parallels API...') that appears superfluous (likely SEO). The first two sentences are concise and informative, but the third is slightly redundant and the keywords add clutter. Could be tighter.

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?

No output schema exists, so the description should clarify the return structure. It only says 'Returns declination for each planet and all parallel/contraparallel aspects' – vague. An agent lacks specifics (e.g., objects vs arrays, planet names, aspect details). Given 7 parameters and no output schema, this is a notable gap.

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 100% with parameter descriptions. The tool description does not add new parameter meaning or constraints; it provides context for the orb usage implicitly. Baseline 3 is appropriate as the schema already documents parameters thoroughly.

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 verb 'Calculate' and the resource 'planetary declinations and find parallels/contraparallels'. It distinguishes from siblings by focusing on declination-based aspects vs. longitudinal aspects (e.g., post_vedic_astrology_aspects). The equivalence explanation (parallels=conjunctions, contraparallels=oppositions) adds specificity.

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 description describes what the tool does but offers no guidance on when to use it versus alternative tools (e.g., post_vedic_astrology_aspects, post_vedic_astrology_planetary_positions). It implies usage for declination aspects but lacks explicit when/when-not examples or references to siblings.

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