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

While annotations already indicate readOnlyHint=false, the description adds valuable behavioral context: 'Watermark customization is applied only for premium callers.' It also clarifies the two image input methods (URL or base64) and the output (hosted meme), going beyond the structured 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?

Two sentences, each earning its place. The first sentence front-loads the primary action and output; the second adds a key business rule. 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's complexity (8 parameters, nested objects, no output schema), the description provides a solid high-level overview: it describes the input modes, the action, and the return value. It does not detail the return structure or edge cases, but the schema covers parameter semantics and the description covers the core workflow, so it is reasonably complete.

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 meaning by explicitly mentioning 'URL or base64' (corresponding to imageUrl/imageBase64) and flagging that watermark customization is premium-restricted, which is not fully captured in the schema's watermark property description. This gives it a 4.

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's function: 'Upload an image by URL or base64, render caption slots on top of it, and return a hosted meme.' This specific verb+resource combination distinguishes it from sibling tools like generate_meme or caption_template, which focus on template-based generation rather than custom uploads.

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 implies when to use this tool (for custom image uploads with captions) but does not explicitly mention alternatives or when-not-to-use cases. It provides context but lacks the explicit differentiation seen in the highest-scoring examples.

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