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

Annotations already declare readOnlyHint=false, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuinely new context: the operation performs a live external crawl, takes ~20 seconds, and returns fresh (non-cached) data, plus a docs link. It does not describe failure modes beyond the 404 trigger, so not a 5.

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?

Three compact clauses: what it does, the latency cost, when to use it, and where docs live. Front-loaded with the action and cost, no filler.

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 and one simple parameter, so the description needs only to convey purpose, latency, and trigger — all present. Minor gap: it never states what the returned 'score' looks like in shape or range.

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% for the single url parameter, so the description must carry the burden. 'any online store' loosely implies url is a store URL, but no accepted format, normalization, or domain constraints are given. Marginal compensation over the bare schema.

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?

States a specific verb (score) and resource (online store) with the key qualifier 'live with a fresh crawl', which cleanly differentiates it from the cached check_store_score sibling. An agent can tell what this does without opening the schema.

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?

Explicitly names the alternative (check_store_score) and the exact condition that selects this tool instead (returns 404). This is a concrete routing rule, not implied usage.

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