guild_get_widget_image_url

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

Annotations already declare readOnly, idempotent, non-destructive. The description adds a critical behavioral trait: 'No REST call is performed', which means the tool is purely a URL synthesizer and the agent decides whether to fetch. This goes beyond annotations and manages expectations about side effects.

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 compact and well-organized via bold headers and bullet lists. Purpose is front-loaded, and each sentence serves a clear function: purpose, usage context, exclusions, and return value.

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's simplicity (2 params, output schema present, annotations available), the description covers all necessary aspects: purpose, usage, non-usage exclusions, and return structure. No significant gaps for an agent to invoke it correctly.

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%—both `guild_id` and `style` have descriptions, including enum values and defaults. The description's Returns section illustrates how `style` is embedded into the URL, but this is only a marginal addition over the schema's existing parameter descriptions.

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 explicitly states the verb 'synthesize' plus resource 'public widget PNG URL', and immediately clarifies that no REST call is performed. It also distinguishes itself from sibling tools by referencing `guild_get_widget` and `guild_get_widget_settings`.

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?

There is an explicit 'When to use' section (embedding a widget image) and a 'When NOT to use' section pointing to `guild_get_widget` for JSON data and `guild_get_widget_settings` for admin settings. This is exactly what this dimension asks for.

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