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

Annotations contain only a title, so the description carries the full behavioral burden and does almost none of it: it never says whether the checker is a live network fetch, whether it mutates anything, what timeout_seconds governs, or whether calls are rate-limited or expensive. Only the word 'wrapper' hints at delegation to another tool.

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?

Two short sentences, front-loaded with the core 'what' and followed by the required inputs. No filler, though the terseness comes at the cost of information rather than from efficient packaging.

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?

An output schema exists, so return values need no explanation, but the description still leaves the decisive gap: with six parameters at 0% schema coverage, an agent cannot know which 'action' strings are valid or what timeout_seconds does. For a dispatcher tool that gates several checkers, that is a material omission.

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% with six parameters, so the description must compensate. It names url, workspace_id, action and payload_overrides but adds no meaning beyond their names, and critically gives no valid values for 'action' (the parameter that selects which checker runs). extra_fields and timeout_seconds are never mentioned at all.

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 concrete verb and resource ('convenience wrapper for the URL-based crawler checkers') and names example checkers (link-extractor, seo-audit-checker, meta-tags-checker), so an agent knows it triggers a crawler check. It does not, however, differentiate itself from the sibling execute_action, which plausibly dispatches the same underlying checkers.

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?

The second sentence tells the agent which fields to supply, but that is largely a restatement of the schema's required list. There is no statement of when to prefer this over execute_action or the specialized crawler_generate_* siblings, and no prerequisites are described.

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