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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description still adds value by pre-empting the misreading that this guide might perform enrollment or scheduling, which the annotations alone would not make obvious.

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?

Two tight sentences, with the positive statement of content front-loaded and the exclusion placed after it. Nothing is padded, though the second clause could have been folded into the first without loss.

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 parameters, a full output schema, and rich read-only annotations, the description only needs to convey scope and it largely does. An explicit note that the returned content is a static reference document rather than live poll data would make it complete.

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 tool takes zero parameters, so parameter semantics have no surface area to document. The description correctly avoids inventing any argument talk and stays focused on the content returned.

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 gives a specific verb and resource ('Read Myndock participation instructions, opt-in follow-up and model reporting'), which is clearly distinct from the poll-listing and policy-getting siblings. It stops short of naming which sibling to consult for adjacent needs, so an agent still has to infer the boundary from the sibling names alone.

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 negative guidance ('Does not enroll, vote or schedule') is genuinely useful for steering an agent away from action-oriented tools when it only wants reference material. It does not, however, state a positive trigger condition or point to alternatives such as get_model_policy or get_poll_format when those are actually wanted.

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