add_svg_gauge

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

With no annotations, the description carries the full burden. It discloses that the tool creates a measure with DataCategory=ImageUrl and explains threshold tinting behavior. It does not mention potential side effects (e.g., overwriting existing measures), required permissions, or return values, but the core mutating nature is implied by 'Author'.

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 a single dense sentence with no wasted words, covering purpose and threshold behavior efficiently. It could be slightly improved with clearer sentence boundaries, but every part contributes useful information.

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 9-parameter tool with no output schema and no annotations, the description explains the core concept and threshold behavior but omits details about side effects, prerequisites, and parameters like size, fillColor, table, or sessionId. It is adequate but not fully 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?

Schema coverage is 67% (6 of 9 params have descriptions). The description adds relational meaning by explaining how valueMeasure, min, max, and thresholds interact to map a value and tint the arc. It does not elaborate on size or fillColor, but those are adequately described in the schema.

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 'authors an SVG ARC GAUGE measure' and specifies it's a semicircular gauge mapping a value onto min..max, rendered in-cell. This distinguishes it from sibling SVG tools like add_svg_progress_bar or add_svg_sparkline.

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 provides clear context: use this tool when creating a semicircular gauge measure for in-cell rendering. However, it does not explicitly mention alternatives or exclusions, though the specificity of 'ARC GAUGE' makes the intended scenario obvious.

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