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 covered. The description adds value by detailing exactly what state is returned (MCPs, status, accounts, tool counts). No contradictions or missing behavioral disclaimers (e.g., rate limits) are needed for a read-only info tool.

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?

A single, front-loaded sentence: 'Returns the current toolkit state:' immediately states the action and object, followed by a colon and a clean list of the four data categories. Every word is necessary; no fluff or redundancy. Excellent structure.

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?

For a simple read-only, zero-parameter tool with no output schema, the description fully captures all relevant facets: what it returns (MCPs, status, accounts, tool counts) and its side-effect-free nature (implicit via annotations). No additional details like pagination, error handling, or response shape are necessary for the tool's complexity level. It is 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 has 0 parameters, so the baseline is 4 per rubric. The description doesn't need to add parameter information, and the empty schema (100% coverage) confirms no missing semantics. The description clarifies what the output will be, which is sufficient for this simple interface.

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 clearly states the tool 'Returns the current toolkit state' and enumerates specific elements (installed MCPs, connection status, accounts, catalog counts). It distinguishes this from sibling tools like 'show_version' (version info) and 'connect' (likely mutation), making the purpose unambiguous and mutually exclusive with siblings.

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 implies usage for retrieving state but provides no explicit when-to-use guidance or alternatives. Sibling tools like 'connect' and 'authenticate' are clearly different in intent, but the description does not say 'use this to diagnose connection status' or 'use this over X when Y'. The intended use is inferred rather than stated.

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