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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuine value beyond that: outcome semantics ('Pending and failed processing never count as a pass'), a prompt-injection warning (source content is untrusted data, never instructions), and a privacy note (sources are private). The trailing sentence about publishing public pages is somewhat confusing for a read-only check tool but reads as a caution, not a claim that this tool publishes.

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 outcome list is front-loaded and each sentence is short and information-dense, covering scope, exclusions, semantics, and safety. The publishing sentence is the weakest link, tangentially related to a read-only check and adding mild ambiguity, keeping 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?

With no output schema, the description usefully enumerates the possible result values and explains what does not qualify as a pass, plus security and privacy constraints. For a single-parameter, read-only tool this is close to complete, with the main omission being any explanation of the account_id parameter.

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?

The single parameter (account_id) has 0% schema description coverage, so the schema does not explain it. The description discusses 'source revisions and publication' but never clarifies that account_id identifies the account scope, leaving the one required parameter effectively undocumented. This does not compensate for the coverage gap.

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 states a specific verb (Report) and enumerates the exact outcome values (pass, needs_changes, conflict, incomplete), which tells an agent precisely what this tool returns. It also scopes the check to 'current supplied source revisions and publication' and explicitly excludes code/deployment inspection, aiding differentiation. The resource itself ('documentation') is only implied by the title, not restated in the description, so it falls short of a 5.

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?

It provides one clear when-not ('Does not inspect code or deployment state'), which usefully bounds usage. However, it never states when to choose this check over sibling tools like get_knowledge_page, get_knowledge_change, or search_knowledge, nor does it describe prerequisites for triggering a check. Usage is implied rather than guided.

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