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

With no annotations provided, the description carries the full behavioral burden but offers no disclosure of traits such as output format, batch limits, rate limits, permissions, or asynchronous behavior. It merely repeats the action verb without any behavioral detail.

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 fragment that restates the name and does not front-load any useful information. While brief, it is under-specified rather than concise, failing to earn its place by adding any agent-relevant content.

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 that this is an image-generation tool with no annotations and no output schema, the description is completely inadequate. It does not explain what 'multiple' entails, how many graphics, what inputs are expected, or what the agent should expect in return, leaving a critical gap for correct 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 100%, so the single parameter 'detail' is technically documented in the input schema, albeit with a generic description. The tool description does not add any additional meaning, but the baseline for full schema coverage is 3.

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 'Slidegen: generate multiple graphics' is essentially a restatement of the tool name, adding only a product prefix. It does not elaborate on what 'multiple graphics' means or how it differs from the sibling tool 'generate_single_graphic' beyond the word 'multiple'. This falls into the tautology category.

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 given on when to use this tool versus alternatives like generate_single_graphic, generate_image, or converse. The description lacks any context about prerequisites, appropriate scenarios, or exclusions, leaving usage entirely to inference.

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