add_svg_icon

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

With no annotations, the description carries the transparency burden. It discloses that it creates a measure with DataCategory=ImageUrl and explains the rules JSON structure, but it does not mention side effects such as whether it overwrites existing measures, requires specific permissions, or what the tool returns. The behavioral detail is moderately rich but incomplete for a mutation tool.

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 information-dense but reasonably sized. It front-loads the core purpose and includes a practical example of the rules format. The sentence is long but every part adds value, and the JSON example is particularly useful despite being verbose.

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 has 6 parameters, no output schema, and no annotations, the description covers the essential concept and rules format but omits prerequisites, error conditions, and return behavior. It is complete enough to understand the tool's core function but leaves gaps for a full invocation.

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 50%, so the description must compensate for undocumented parameters. It adds significant meaning for 'rules' by providing a concrete JSON example and clarifies 'valueMeasure' as the measure tested against bands. However, it leaves 'name', 'table', and 'sessionId' without explanation, relying on the agent's general knowledge of similar tools.

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 uses a specific verb 'Author' plus the resource 'SVG THRESHOLD ICON measure' and explains the exact behavior: rendering a unicode glyph colored by value bands. This clearly distinguishes it from sibling SVG tools like add_svg_chip or add_svg_sparkline by emphasizing the threshold/banding logic.

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 implies when to use the tool (when you need a threshold icon measure) but does not explicitly state alternatives or exclusions. While the threshold banding concept is clear, there is no direct comparison to similar SVG tools or 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.