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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well established. The description adds context about what is returned (connection status, accounts, catalog counts) but does not disclose whether the data can be stale, whether it performs a live network check, or any potential latency. No contradiction with annotations exists.

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, front-loaded sentence that immediately states the tool's purpose and then lists the specific components of the returned state. Every word adds value and there is no filler or redundancy.

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, no output schema, and annotations covering the read-only/idempotent safety profile, the description is sufficient. It enumerates what the agent will learn from the tool: installed MCPs, connection status, connected accounts, and catalog tool counts. An agent has enough to decide when to call it and what to expect back.

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, so there are no parameter semantics to describe. Per the baseline for zero-parameter tools, the description need not explain parameters. The description focuses on the return value, which is appropriate.

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 names the exact resource ('current toolkit state') followed by a detailed breakdown of what that state contains: installed MCPs, connection status, connected accounts, and catalog tool counts. This clearly distinguishes it from sibling tools like calculo_* or authenticate, which perform different actions.

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 makes it evident that the tool is for inspecting toolkit status, and with zero parameters it is trivial to invoke. However, it does not explicitly state when to prefer this over related tools like show_version or connect, nor does it provide any exclusion criteria. Usage context is implied rather than stated.

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