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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds useful behavioral context beyond them: 'release' is read live from GitHub, and 'mcp_tools' describes tools that run on the developer's own machine over stdio rather than on this server. It does not mention caching, latency, or any limits on live GitHub reads, but the key behavioral distinction is disclosed.

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 a single dense sentence, but it is front-loaded with the core action and then enumerates topics in a logical order. Every clause carries information; the semicolon-heavy structure is slightly harder to scan than a short bulleted breakdown would be.

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?

Given that an output schema exists, the description need not document return shape, and it still explains the content of each topic well enough for an agent to choose correctly. The only minor gap is that it does not clarify whether the reference lists are exhaustive or paginated, though for a small reference tool this is likely unnecessary.

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 100%, so the schema already documents every parameter and all enum values. The description still adds meaningful semantic detail for the required 'topic' parameter by explaining exactly what each topic returns and when it is useful, which goes beyond the schema's one-line 'Which reference list to return'.

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 specific verb and resource ('Return one reference list about agent-manager') and then names all four topic values, making the tool's scope immediately clear. It also distinguishes the 'agents' topic from a general docs lookup by tying it to the specific question 'does agent-manager support X'.

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 gives clear topic-by-topic context: use 'agents' to answer support questions, use 'release' for the newest GitHub release and install commands, and use 'mcp_tools' to see tools registered into sessions. It does not explicitly contrast this tool with siblings like get_doc_page or search_docs, so it stops short of full when/when-not routing.

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