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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds 'exact metadata and source URLs' as return expectations, but it does not disclose error behavior, authentication needs, or rate limits. This is acceptable for a simple read-only getter but adds limited extra context.

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 with no filler, front-loading the key action ('Get') and the output ('exact metadata and source URLs'). It is appropriately concise for a tool with one parameter.

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?

This is a simple, low-risk read-only tool with strong annotations, so the description is mostly adequate. However, there is no output schema, and the description does not clarify the return format, error behavior, or how to choose between this and sibling tools. These gaps keep it from being fully 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 description coverage is 0%: the description does not mention the 'slug' parameter at all. The schema defines only name, minLength, and maxLength. For a low-coverage case, the description should compensate by explaining what a slug is or how to use it, but it does not, so the agent must rely solely on the parameter name.

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 uses a specific verb and resource: 'Get exact metadata and source URLs for one published Web3icon asset.' It clearly indicates this tool retrieves a single published asset, distinguishing it from siblings like search_assets (searching) and get_embed_code (embedding).

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?

Usage context is implied: the description says 'for one published Web3icon asset,' so an agent can infer it is for fetching a known asset. However, it does not explicitly state when to use this tool versus get_embed_code or search_assets, nor does it mention any exclusions.

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