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

Annotations already declare readOnly/idempotent/non-destructive, so the description appropriately spends its words on coverable gaps: the data-quality constraint (only self-reported birth times, with source attribution), the failure mode (missing name = unknown), and what comes back (big three, placements, source, page link). No auth or rate-limit detail, but for a read-only lookup that is minor.

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?

Three tight sentences, front-loaded with the identification of the collection, then the data constraint, then the return payload. The parenthetical example list is slightly long but earns its place by showing the event-as-name case.

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?

With no output schema, the description usefully enumerates return contents (big three, placements, source, page link) and warns about the empty-result case. Complete enough to call correctly; only the sibling disambiguation is missing.

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% and the schema already documents the single name parameter with the same examples (Billie Eilish, Bitcoin). The description adds little beyond reaffirming that the name may be a person or an event, which is baseline territory.

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 resource (birth chart) and a specific scope (celebrities or famous moments from Pluto Garden's sourced collection), with concrete examples like Billie Eilish and the Moon landing. It does not explicitly contrast with the sibling birth_chart, so an agent must infer the difference from the 'collection' framing.

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 implies when to use it (you want a pre-sourced chart for a known public figure or event) and gives one useful exclusion — a missing name means no self-reported time exists. It never names the alternative birth_chart for user-supplied chart data, so routing between siblings is left to inference.

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