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

Annotations indicate readOnlyHint=false (write) and no destructive hint. The description adds important behavioral context: pricing ($0.01 per call, paid via x402) and default output characteristics (SVG+PNG, squircle, 1024x1024). No contradiction with 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 a single, well-structured paragraph with all necessary information front-loaded. Every sentence adds value—purpose, defaults, options, return format, pricing. No wasted words.

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 8 parameters with full schema coverage and an output schema (not shown), the description is complete. It covers output format (SVG+PNG), default values, pricing, and key parameter explanations. No gaps for an agent to make wrong assumptions.

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 100%, so baseline is 3. The description adds semantic value beyond schema: explains gradient with 2 colors, enumerates shapes, specifies size range (64-1024), and padding fraction range (0.05-0.35). This helps the agent understand parameter interplay.

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 generates an app-ready icon from Font Awesome icons, specifying format (SVG + PNG base64), default size (1024x1024) and shape (squircle). It distinguishes from siblings like get_icon_search (search only) and post_logo_generate (likely different).

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 explains when to use (to generate an app icon) and mentions that searching returns alternatives. However, it does not explicitly state when not to use or compare with the sibling get_icon_search, which could be used for icon search without generation.

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