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

Annotations already disclose that this is a read-only, idempotent, and non-destructive operation, so the bar for added transparency is lower. The description adds useful context about what the response contains, but it does not go further to explain behavior like whether this makes network calls to probe MCP connections or whether the output is stable over time. This is acceptable, though not exemplary.

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 that packs in the exact resource and the categories of information returned. There is no filler, no repetition of the name, and no unnecessary background. Every word adds meaning.

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?

A zero-parameter tool with no output schema depends on the description to explain what the agent will receive; this description does that comprehensively by naming — installed MCPs, connection status, connected accounts, and catalog tool counts. For a simple, read-only introspection tool, this is complete enough to drive correct selection and invocation.

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 accepts zero parameters, so there are no parameter semantics to explain. The description correctly does not waste words on parameters, and the baseline of 4 applies for no-parameter tools.

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 uses a specific verb ('Returns') and clearly identifies the resource ('current toolkit state'), then enumerates key elements: installed MCPs, connection statuses, connected accounts, and catalog tool counts. This distinguishes it from the listed siblings, especially show_version, because it describes an overall state inventory rather than just a version string.

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 intended use is implied but not explicit: if an agent needs an overview of the current toolkit state, this tool is the natural choice. However, the description does not say when not to use it, nor does it contrast it with related peers like connect, authenticate, or show_version, so contrastive guidance is missing.

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