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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds what information is returned, which is useful context beyond annotations. However, it does not disclose any additional behavioral nuances (e.g., whether results are cached, network calls involved, or error handling). With annotations doing the heavy lifting, a 3 is appropriate.

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 front-loads the primary action ('Returns the current toolkit state') and then lists the specific components. Every phrase adds value; there is no fluff or redundancy. It is exceptionally concise and well-structured.

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 no output schema exists, the description carries the responsibility of conveying what the tool returns. It does so by enumerating the four key pieces of state: installed MCPs, connection status, accounts, and catalog tool counts. This is adequate for a simple info-retrieval tool, though it could additionally note whether the output is a flat list or nested structure. The tool's simplicity means this level of detail is sufficient, but not exhaustive.

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 zero parameters, so the schema is trivially complete (100% coverage). Per the rubric, a baseline of 4 applies for 0 parameters. The description adds no parameter-specific semantics (none needed), but this does not detract—the baseline stands because there is no parameter burden to compensate for.

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') plus a clear object ('current toolkit state') and enumerates the actual content (installed MCPs, connection status, accounts, catalog tool counts). This clearly distinguishes it from siblings like show_version (version info) and connect (establishing connections), leaving no ambiguity about the tool's function.

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 the tool is for inspecting the toolkit's current state, which is the natural pre-check for actions like connecting or authenticating. However, it does not explicitly state when to use it over alternatives (e.g., show_version) nor any exclusions. The purpose is clear enough for context, but lacks explicit guidance.

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