infographic_create

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

The description includes 'requires confirm=true', which is a useful behavioral gate, but this information is already present in the confirm parameter schema ('Must be true to start generation'). With no annotations provided, the description carries the burden of disclosure, yet adds no further details about side effects, return values, or generation process.

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 sentence, extremely concise and front-loaded with the core purpose. It wastes no words, though it is quite sparse; still, it is appropriately brief for the limited content it conveys.

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 creation tool with 7 parameters and no output schema, this description is under-specified. It lacks any indication of return values, asynchronous behavior, or parameter interplay. The schema covers parameter meanings, but the overall tool context is incomplete.

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 the baseline is 3. The description adds no extra semantic meaning beyond the schema; it only restates the confirm requirement already documented in the schema. However, since all parameters are well-described in the schema, this is acceptable.

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 states 'Generate an infographic' with a specific verb and resource, clearly distinguishing it from sibling creation tools like slide_deck_create or report_create. The appended confirmation note is a behavior, not a purpose, but does not obscure the core function.

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?

No guidance is provided on when to use this tool versus other creation tools such as audio_overview_create or video_overview_create. The description only states the action, leaving the agent to infer usage context entirely from the tool name.

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