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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, so the mutating/non-idempotent profile is partly covered. The description still adds real value: expected latency (~20s), that it updates the stored score, and that repeated calls can trigger new scans — side-effect and cost context not derivable from the hints alone.

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?

Dense but front-loaded: purpose first, then routing, then requirement/side effects, then docs link. Every sentence earns its place, though 'repeated calls can trigger new scans' partially restates the non-idempotent implication already given.

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 conveys the gist of the result (a store score) plus latency and the fact that a stored score is updated. It does not describe the score's shape or range, but nothing essential for correct invocation is missing.

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 0% for the single url parameter, so the description must carry it, and it does: 'requires a full HTTP(S) URL', which clarifies scheme/format beyond the bare 'string/uri' schema. It stops short of stating length limits or validation failure behavior.

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+resource (score a store) with the defining trait 'live with a fresh crawl (~20 seconds)', which immediately separates it from the cached sibling check_store_score. An agent can classify it 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?

Explicit trigger conditions ('when check_store_score returns 404 or a fresh scan is explicitly requested'), an explicit alternative to use otherwise ('check_store_score ... to retrieve an existing result without crawling'), and a routing note to check_product_trust for a different evidence type. This is textbook when/when-not/alternatives.

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