chart_wheel_on_house_click

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

The description discloses that it is an event handler and is read-only, consistent with the readOnlyHint annotation. It adds the automatic invocation detail, which aids understanding. No contradictions.

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, front-loaded with purpose and followed by a usage note. No wasted words.

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 simple event handler with no output schema, the description covers purpose, automatic invocation, and return value. Annotations provide readOnlyHint. Sibling tools are many, but the description clarifies it is a UI callback, making it complete.

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?

Input schema has 100% coverage with descriptions for all parameters. The tool description does not add further parameter details beyond stating it returns meaning, which matches the baseline for high schema coverage.

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 clearly states it is an event handler for clicking a house cusp or number, and that it returns astrological meaning. It is distinct from sibling click handlers like chart_wheel_on_aspect_click and chart_wheel_on_planet_click.

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?

Explicitly states the tool is called automatically by the chart UI and that the AI agent does not need to call it directly. This provides clear guidance on when not to use it.

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