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

Goes well beyond the annotations: discloses robots.txt compliance, the 40s server-side budget versus the 25s call wait, that a timed-out scan likely continues and can be found via helpcenter_list_imports, and the destructive-ish side effect that scanning a different address cancels a prior un-run import (consistent with destructiveHint=true). The only gap is that it does not state explicitly that the returned import/plan objects can be very large or what 'limit' means.

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?

Front-loaded with purpose and the 'Imports nothing yet' caveat, then workflow, then failure modes, then args and return shape. Nearly every sentence carries operational value; slight density in the timeout paragraph keeps it from a 5.

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?

For a tool with real side effects, a long-running remote fetch, and no output schema, the description supplies the return shape sketch ({ import: { id, platform, importable, status, plan, ... } }) plus the instruction to keep the id. Timeout, credential-refusal, and unsupported-platform outcomes are all anticipated.

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 100%, so the baseline is 3. The prose restates the confirm_ownership rule ('not needed while unclaimed; required once claimed') and the 'only send it when the user has said so' guard, but that is largely duplicated in the schema, and the description never mentions agent_key, which the schema covers thoroughly.

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 ('Read a public Zendesk Guide, Intercom, ... help center') and immediately bounds the output ('its categories, articles and languages, and where each language lands here'). The clarifying sentence 'Imports nothing yet' separates it decisively from helpcenter_run_import, which is its nearest sibling.

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 the full pipeline explicitly: scan, optionally helpcenter_choose_import, then helpcenter_run_import, then helpcenter_get_import. It also names the fallback for refused sources (helpcenter_request_migration) and the recovery path on timeout (wait ~20s, check helpcenter_list_imports rather than rescanning). When-to-use and when-not-to-use are both covered.

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