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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds some genuine context beyond the schema by noting 'supporting and opposing evidence', 'unresolved source keys', and 'sensitive-house restrictions', hinting at output structure and handling caveats, but it says nothing about computational cost, required birth-data fidelity, or error behavior.

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?

A single long run-on sentence enumerating outputs; it is dense and wastes no words on fluff, but it is a comma-list rather than a front-loaded statement of purpose, which weakens structure.

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 natal-chart analysis tool with 9 parameters and an anyOf location constraint, the description is inadequate. Since an output schema exists it need not restate the return fields, yet it does only that while omitting the usage and parameter context an agent actually needs to call it correctly.

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 is expected to compensate — and it provides zero parameter guidance. It never explains the house selector, the birth date/time/name inputs, or the place-vs-coordinates alternative that the anyOf enforces.

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 name and title establish the operation (analyze one natal house), but the description itself opens with 'Returns...' and enumerates outputs rather than stating what the tool does. An agent gets the gist from name+title but not from the description text, and there is no differentiation from siblings like analyze_chart_topic or analyze_marriage_structure.

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?

There is no indication of when to use this tool versus the many other analyze_* siblings, nor any prerequisites or exclusions. Usage must be inferred solely from the tool name.

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