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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description does add a genuinely useful behavioral distinction: broken links are 'the only problems' while the remaining categories are informational. It says nothing about cost, permissions, or pagination.

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?

It is a single dense run-on sentence loaded with parentheticals, so it is not well front-loaded or scannable. Every clause carries real content, so it is not padding, but the structure could be broken into the primary result plus a short list.

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?

With no output schema, the description usefully enumerates the returned categories, which is exactly what the agent needs. Combined with the annotations covering safety, the definition is largely complete, missing only usage routing and any note on result size or cost.

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 only 33% (only 'workspace' is documented), so the description must compensate, and it largely does: it defines stale_days via 'past their stale_after date, or unchanged stale_days while pages they link to changed' and long_page_words via 'pages over long_page_words'. The definitions are slightly convoluted but they do give the parameters meaning beyond the schema.

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 ('Check the wiki') and then enumerates precisely what the check reports, so an agent can tell it apart from list_pages/search_pages which just retrieve content. The purpose is clear, though the enumerated output list is long enough to blur the headline.

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 guidance, and no alternatives are named despite many sibling read tools (list_pages, search_pages, page_history). The agent must infer that this is the diagnostic tool for detecting broken links.

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