Bi-Wheel (SVG)

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds only 'standard bi-wheel layout,' which does not disclose additional behavioral traits beyond annotations. It fails to mention any side effects, permissions, or output characteristics.

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 an example request body. It is front-loaded with the key purpose and layout summary. Every element serves a purpose with no filler.

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 bi-wheel chart with nested parameters and no output schema, the description is insufficient. It does not explain what the output contains (e.g., SVG vs JSON, aspect lines, house cusps) or how to interpret the result. The example only partially compensates.

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 67% description coverage for parameters. The description provides an example request body that illustrates usage but does not add significant meaning beyond the schema. For a tool with nested objects, the example helps contextualize parameter usage, but value is marginal.

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 bi-wheel with inner natal and outer transit/progression rings, using the phrase 'Standard bi-wheel layout.' This distinguishes it from siblings like render_tri_wheel and other chart rendering tools.

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 does not provide any guidance on when to use this tool versus alternatives. It lacks explicit context such as choosing between transit or progression for the outer ring, or comparing with other render tools. The example is present but does not explain selection criteria.

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