diagnose_error

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

With no annotations, the description carries the full burden. 'Attempt download' implies a possible network fetch and side effect, but it never says whether a file is saved, whether this is a read-only probe, what permissions or rate limits apply, or whether failures throw versus return an error payload.

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?

A single tight sentence, front-loaded with the verb and resource, with no filler. It is arguably too short rather than padded, which is the preferred failure mode.

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 annotations and no output schema, so the description must explain what 'detailed error' actually contains and what the caller gets back on success versus failure. It does neither, leaving the diagnostic result shape entirely undefined.

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% and both parameters are documented in the schema, so the baseline of 3 applies. The description actually adds a small point of confusion by referring to a 'page URL' rather than the integer page plus base_url the schema defines.

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 names a specific verb (diagnose) and resource (a page URL), and the phrase 'attempt download and report detailed error' distinguishes it from the plain download_page sibling by stating it returns diagnostics rather than content. Misfit: it says 'page URL' while the schema actually takes a page number plus a base_url, which muddies the resource identity slightly.

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?

There is no explicit when-to-use or when-not-to-use guidance. The diagnostic intent implies it is for troubleshooting failures, but the siblings download_page and inspect_page are never named, so the agent must guess which tool to call first.

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