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

Annotations provide no safety hints (all false), so the description carries full burden. It adds input constraints (no contact details, URLs, wallet addresses, private data), but does not disclose what happens after the request (e.g., confirmation, persistence, or response format). This is a partial disclosure, not a complete behavioral picture.

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 concise and front-loaded with the purpose, followed by usage context and constraints. Each sentence adds value without redundancy.

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 simple request tool with no output schema and no annotations, the description covers purpose, timing, and input restrictions, but lacks details about the outcome or any follow-up. It is adequate but not exhaustive.

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 only 33% (only 'concept' has a description). The description does not directly explain 'concept' or 'useCase', though it implicitly covers 'category' by mentioning icon/illustration/animation. This does not compensate for the low schema coverage.

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 a specific action ('Request a Web3 icon, illustration, or animation that is missing from the catalog') with a clear resource and condition. It differentiates from siblings like search_assets (which finds existing assets) and get_asset (which retrieves specific assets).

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?

Explicit guidance is provided: 'Use this after search_assets returns no suitable result.' This clearly defines when to use this tool and implicitly differentiates it from the search tool. Additional constraints ('Do not include contact details...') give further usage rules.

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