Chart Element Interpretation

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the tool is clearly a read operation. The description adds no additional behavioral context beyond the annotations; it only repeats the cost and group. It does not disclose any new traits like auth needs, rate limits, or response 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?

The description is extremely concise: two sentences plus a group/cost line and an example. It is front-loaded with the purpose. Every element earns its place without waste.

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?

Given the tool's moderate complexity (single element interpretation with nested input), the description includes the context, cost, and an example. It lacks output format details, but that is acceptable since no output schema is provided. It is fairly complete for its purpose.

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?

The input schema has 100% description coverage, already documenting the required fields and defaults. The description adds value by providing a concrete example request body showing the structure and usage, which helps the agent construct valid input.

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 that this tool provides 'AI interpretation of a single chart element (planet/house/aspect) in context,' which is a specific verb-resource pair. It is distinguished from siblings like interpret_natal (whole chart) and interpret_placement (specific placements) by focusing on a single element.

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?

The description says 'Useful for chart-detail pages,' implying a specific context, but it does not explicitly state when not to use the tool or mention alternatives among the many interpretation tools. No exclusions or comparative guidance is provided.

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