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

Goes meaningfully beyond the annotations: it discloses that the submission is stored as pending and is not published, and that sign-in is required — neither of which is inferable from readOnlyHint=false/destructiveHint=false. It doesn't cover review latency, edit-after-submit, or limits, but the core workflow state is clear.

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 sprawling run-on sentence chains a dozen unrelated editorial requirements before reaching the actual tool behavior, and the tool's real semantics sit at the very end. Front-loading is inverted: the least tool-relevant content comes first.

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 needn't be explained, and the pending-review plus sign-in facts are covered. But for a 5-parameter, 0%-coverage mutation tool, the total absence of parameter documentation and of the propose_new_article alternative leaves real gaps for correct invocation.

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%, so the description carries the full burden, yet it explains nothing about path, summary, or detail — not even their length limits or formats. The only parameter-adjacent content is "trace every quote and fact to a named source," which hints at the sources array but gives no structure or count guidance.

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 operative statement — "Submit a change to a published page" — is specific in verb and resource, but it arrives only after a long run-on list of content requirements, so an agent skimming the opening sentences would mistake this for a style guide rather than a mutation tool. It never names propose_new_article, which is the sibling that handles new pages, so the published-vs-new distinction is left implicit.

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?

Useful sequencing is given: "Read get_submission_guidelines first" and "check_existing_coverage is a suggestion and does not block." The "change to a published page" phrasing implies new pages belong elsewhere, but no alternative tool is named and no explicit exclusion is stated.

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