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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond that by naming the two source texts and, critically, flagging that results are unreviewed drafts rather than vetted rules — a quality caveat the agent cannot get from structured fields. It does not address determinism or what happens with incomplete birth data.

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 sentences, both front-loaded and information-dense with no filler. The parenthetical enumeration of life areas slightly duplicates the schema enum but reads as useful scannable context. The second fragment is terse to the point of being cryptic.

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?

An output schema exists, so return-shape explanation is correctly omitted, and the description notes the citation/effect/weight payload. However, for a 9-parameter tool with a two-branch location requirement and a crowded sibling set of 80+ astrology tools, the description leaves the calling contract under-specified. It is minimally viable but does not prepare an agent to construct a valid call from the description alone.

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% across 9 parameters, so the description needed to compensate and does not. It never explains the anyOf location branch (place label vs. latitude/longitude plus IANA timezone), the required date/time/topic triad, or the timezoneOffset fallback. The only indirect coverage is echoing the seven life-area values that the topic enum already lists.

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 names a specific verb and resource — it runs life-area rule cards drawn from two named source texts and returns the matching verses — and enumerates the seven supported life areas, which maps cleanly to the topic enum. It stops short of naming which sibling it replaces (analyze_chart_topic, search_reviewed_rules), so the agent must infer the boundary. The closing 'Located drafts, not reviewed rules' does supply a distinguishing qualifier.

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 explicit when-to-use or when-not guidance is given, and no prerequisites (birth date, time and place/coordinate requirement) are stated. 'Located drafts, not reviewed rules' is a status disclosure rather than routing guidance toward search_reviewed_rules or analyze_chart_topic. The agent is left to guess whether this is the draft-tier counterpart of the reviewed-rule tools.

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