asset_generate_favicon

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

Description discloses output files (favicon bundle) but does not detail side effects or state changes. Annotation 'openWorldHint: true' is consistent, but additional behavioral context (e.g., whether it modifies input assets) is missing.

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?

Two sentences: first states purpose and output, second gives mode guidance. No redundant information; every sentence adds 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?

Despite no output schema and low parameter coverage, the description does not fully compensate. It lacks detail on required input semantics and does not clarify the roles of nested objects or optional parameters, making the tool less complete for autonomous 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 description coverage is 0%, yet the description only explains the 'mode' parameter (three values) and hints at output. Other parameters like 'brief', 'brand_bundle', 'existing_mark_svg' are not explained, leaving the agent with insufficient semantic understanding.

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?

Clearly states 'Generate a favicon bundle' and lists specific output files, distinguishing it from sibling tools like logo or app icon generators. Mentions three modes, with inline_svg recommended for simple glyph marks.

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?

Provides guidance on when to use each mode ('inline_svg is the best fit for simple glyph marks') but does not explicitly contrast with sibling tools or give when-not-to-use advice.

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