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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, so the description's real addition is the payment requirement: $0.003 USDC per call via x402 on eip155:8453, plus the breadth of the bot database (35+ including GPTBot, ClaudeBot, CCBot). It does not say what happens with a malformed or empty UA, nor whether unknown agents return null vs. 'unknown'.

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, front-loaded with purpose, then coverage detail, then pricing. The bot-category enumeration ('search engines, AI crawlers, social preview fetchers, SEO tools, monitors and HTTP libraries') is informative but slightly sprawling and could be trimmed without loss.

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?

No output schema exists, and the description compensates by listing the returned fields (browser/version, engine, OS/version, device class, bot identity). For a one-parameter, no-side-effect tool that is nearly complete; the only gap is error/edge-case behavior for unparseable input.

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% and the description never mentions the single `ua` parameter, its 2000-character cap, or that it is the only required input. The parameter name is self-explanatory and there is only one, which limits the damage, but the description adds nothing the schema does not.

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?

Specific verb ('Parse') plus resource ('User-Agent') followed by an explicit enumeration of the parsed fields (browser, engine, OS, device class, bots). No sibling tool (url_parse, web_headers, web_extract) does UA parsing, so an agent can route here unambiguously.

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 is implied rather than stated: an agent with a UA string and an interest in bot/device classification will infer this is the tool. There is no explicit 'use when...' clause, no exclusions, and no mention of an alternative for related needs such as header inspection (web_headers) or URL breakdown (url_parse).

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