Cosmogram — Hamburg School 90° dial (SVG)

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

Annotations indicate readOnly, idempotent, and non-destructive behavior, which the description does not contradict. The description adds that it plots planets modulo 90 across quadrants, but does not elaborate on side effects, return format, or authentication needs. It provides some behavioral context beyond annotations.

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 concise with two sentences plus a group tag and example. It is front-loaded with the core functionality. No wasted words, though the structure could be slightly improved by separating the example into a separate section.

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 complexity of a cosmogram rendering tool with many params and no output schema, the description is brief. It lacks explanation of the output format (though title mentions SVG), interpretation of quadrants, or prerequisites. Adequate but leaves gaps for deeper understanding.

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% coverage with descriptions for nested objects. The tool description includes an example request body but does not add new meaning beyond what the schema already provides. Baseline score is appropriate.

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 the tool renders a Cosmobiology 90° dial, plotting planets modulo 90 across four quadrants (Cardinal/Fixed/Mutable). The title and name are specific, and it distinguishes from siblings like 'cosmobiology_cosmogram' and 'chart'.

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 includes a '[Group: Visualization]' tag implying it is a visualization tool, but does not explicitly specify when to use this tool over alternatives like 'cosmobiology_dial_90' or other cosmobiology tools. No exclusions or when-not-to-use guidance is provided.

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