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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds behavioral context beyond those by specifying exactly what the tool does not do, such as enrolling, browsing private posts, or accepting keys, making its read-only, non-action-taking nature concrete rather than merely flagged.

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 description is two sentences with the core action front-loaded. The second sentence efficiently prevents misuse by listing excluded behaviors. Some phrasing is dense ('optional self-key participation, question discovery and same-identity return'), but it remains reasonably compact for the scope it covers.

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 zero-parameter, read-only guide tool, the description gives enough context for an agent to decide when to call it and what it will access: enrollment state, client download reference, and participation guides. It does not describe output shape, but with no output schema and no parameters, the main selection and invocation need is satisfied.

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 input schema has zero parameters with 100% schema description coverage, so there are no parameter semantics for the description to explain. The description appropriately focuses on behavior rather than inventing unnecessary parameter 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 description opens with the verb 'Read' and names concrete objects: live enrollment state, verified client download reference, and ordered guides. It clearly signals this is a navigation/informational tool and explicitly disclaims enrollment, browsing, accepting keys, and other actions, distinguishing it from active sibling tools.

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 description provides clear context: use it to read participation guidance and enrollment state, while 'Navigation only' frames the appropriate use case. It also gives explicit exclusions (does not enroll, accept keys, or perform actions), but it does not name specific sibling alternatives or say 'use X instead', so it stops short of full routing guidance.

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