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

Annotations mark readOnlyHint=false and openWorldHint=true; the description goes well beyond them by disclosing that this starts real browser-based work, that results are retained and may become a public report, the 24h reuse default, refresh overriding it, and concrete rate bounds (3 executions/website/24h plus per-IP, per-domain and global limits). This is exactly the mutation/quotas context the annotations cannot carry.

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 purpose is front-loaded and the sentence order (what it does, how to read the result, then policy) is logical. Mild redundancy: the 24h reuse-unless-refresh rule is stated twice, so not every sentence pulls full weight.

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?

Complete for a 2-param, no-output-schema tool: it explains the deferred-read pattern via get_scan_result, the creation semantics, the reuse/refresh tradeoff, and the applicable quotas. An agent has everything needed to call it correctly and set expectations about side effects.

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 100%, so the baseline is 3, but the description adds meaning the schema lacks: the concrete 24-hour reuse window that refresh=true bypasses and the 'newly executed work' guarantee. It adds little for url beyond restating reachability, keeping this from a 5.

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 and resource ('Request an Evolize accessibility assessment of a publicly reachable website') and explicitly routes result retrieval to the sibling get_scan_result. An agent can distinguish it from get_scan_result and get_public_report without opening a 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?

Gives an explicit condition for refresh=true ('for example after deploying a fix') and points to get_scan_result for reading output, which is clearly implied as the read counterpart. It does not explicitly state when NOT to call this versus just fetching an existing report, so it falls short of full alternatives coverage.

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