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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: 'supporting and opposing evidence', 'unresolved source keys' and 'sensitive-house restrictions' signal evidence-quality and possible restriction behavior, but these terms are left undefined, so the added value is partial.

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?

It is a single dense sentence with no filler, which is good, but it is an undifferentiated comma-separated output dump rather than a front-loaded statement of function followed by supporting detail. Short, but not well structured.

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 already exists, so the description's entire content — a list of return fields — is largely redundant. Meanwhile the elements an agent actually needs (when to use it, how the 9 inputs including the anyOf location branch work, what restrictions apply) are absent. Incomplete for a tool of this complexity.

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 must compensate and does not: it never mentions date, time, the 1-12 house input, the place-vs-latitude/longitude/timezone anyOf requirement, or timezoneOffset. Only 'the selected house' obliquely gestures at the house parameter.

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 enumerates what is returned (house, lord condition, occupants, functional lordship, evidence) which lets a reader infer this is a per-house analysis tool, but it never states the action in verb+resource form and offers no differentiation from the many sibling analyzers (analyze_career_structure, analyze_marriage_structure, analyze_finance_structure, etc.). The purpose is recoverable but vague rather than sharply stated.

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 when-to-use guidance, no prerequisites (e.g. chart data required), and no routing to alternatives such as the topic-specific structure analyzers or analyze_chart_topic. The agent must guess whether this generic house tool or a specialized sibling is appropriate.

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