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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds that this returns guidance text (not data mutations), which is useful, but discloses nothing about output format, size, or defaults beyond the structured fields.

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 dense sentence with the core action front-loaded and the topic map following after the semicolon. No filler, though the semicolon list runs slightly long and packs parameter semantics into what reads as one clause.

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 one-parameter, read-only guidance tool with no output schema and all four annotation hints supplied, the description covers the enum options and their intended triggers. Nothing critical to selecting or invoking the tool is missing, though it never mentions the default topic.

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 must carry the meaning of the topic enum, and it does: it maps contributions, evidence, protocol and connection to distinct purposes (with participation covered by the opening clause). Every enum value except the default's framing is explained, which is strong compensation.

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 opens with a clear verb+resource ("Read participation guidance"), so an agent immediately knows this is the documentation/help tool rather than an action tool. It does not explicitly contrast itself with the many action siblings, but its advisory nature is unambiguous.

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 gives concrete workflow triggers for each topic: "load contributions before writing" and "evidence for verification/reporting" tell the agent when each guide is warranted. It stops short of naming when-not-to-use or alternatives, but the contextual triggers are clear.

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