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

Annotations already declare readOnlyHint and openWorldHint=false; the description adds the meaningful privacy disclosure 'Nothing is stored', which is the kind of context annotations cannot express. It also identifies what the tool cannot compute, preventing over-reliance.

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-loaded with the outputs, then the input constraint, then the privacy note, then the scope limit. Dense with no filler, though the four-clause structure is slightly dense for a one-parameter tool.

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?

There is no output schema, but the description names the three computed values and the guide links, so an agent knows what to expect. The exclusion of advanced astrological outputs is covered; only the exact response shape (e.g., how links are formatted) is left implicit.

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 itself documents the YYYY-MM-DD format and 1900-or-later/not-future bounds, so the baseline is 3. The description adds value by explicitly forbidding additional personal data, reinforcing the single-parameter contract beyond the schema's additionalProperties constraint.

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 (calculate) and precisely enumerates the three outputs: Life Path number, Western Sun sign, and Chinese zodiac animal, plus the linked reading guides. This is far more than a restatement of the title and lets an agent know exactly what comes back.

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?

Clearly scopes usage: only a date is needed, sensitive extras (names, times, places) must not be sent, and extended features (Moon, rising, houses, full combined reading) require the website form. It does not explicitly route to the siblings get_chinese_zodiac_year or get_unified_reading_options, so a small gap remains.

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