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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new operational context: the OAuth Bearer token requirement, which the annotations do not convey, plus a concrete inventory of what the payload contains. It stops short of noting response size or rate limits when include_tools is true.

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?

Highly dense and front-loaded: the resource description comes first, the sibling routing second, the auth prerequisite last, with no filler. It is written as one long compound sentence, which makes it slightly harder to scan than it could be, but nothing is redundant or padded.

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?

There is no output schema, and the description compensates by describing the return shape at both levels (toolset and optional per-tool entries with safety flags). Combined with the named prerequisite (OAuth Bearer token) and the zero-required-parameter signature, an agent has everything needed to call it correctly on the first attempt.

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 coverage is 100%, so the baseline is 3. The description still earns a point by explaining the tradeoff behind include_tools — that tool entries omit descriptions and parameters because search_tools and describe_tool carry those — which frames why an agent would or wouldn't set it. The _meta analytics block is left entirely to the schema.

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?

Opens with a concrete metaphor-plus-verb framing ('The map of this server') and then enumerates exactly what is returned: every toolset with id, title, one line, and tool count, optionally each tool's name, title, and safety flags. It explicitly differentiates itself from all three siblings by assigning each a distinct role.

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?

Explicitly routes the agent: use search_tools to find a tool by capability, describe_tool to read one definition, call_tool to execute, leaving list_toolsets as the orientation step. The condition for the include_tools variant is also spelled out, so selection between tools and between parameter modes is unambiguous.

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