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

Annotations declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent already knows it's a safe read operation. The description adds valuable context by specifying what the state includes (installed MCPs, connection status, accounts, catalog counts) and the non-real-time nature implied by 'current state'. It doesn't contradict annotations and enhances them by detailing the data scope.

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 one sentence, front-loaded with the primary action, and contains no wasted words. Every clause adds a distinct piece of information about the return content, making it both concise and complete. It is appropriately sized for a zero-parameter tool with no complex 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?

Given the tool's simplicity (no params, no output schema) and the rich annotations (readOnly, idempotent, non-destructive), the description fully covers what an agent needs to know: it tells the agent what the tool does and what it returns. There is no missing information about behavior, side effects, or return format, given that the return format is inherently structured by the catalog description.

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 provides no parameter details. With 100% schema coverage (vacuously, since there are no properties), the description doesn't need to explain parameters, but it does need to clarify what the tool returns, which it does. It earns a baseline 4 due to no parameters, and adds value by describing the retrieved state.

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's purpose with a specific verb ('Returns') and resource ('current toolkit state'), and enumerates the exact information it provides (installed MCPs, connection status, accounts, and catalog tool counts). This distinguishes it from siblings like show_version and report_bug, which focus on version and issue reporting, respectively.

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 this tool is for checking the toolkit status, which is useful before operations. However, it doesn't explicitly state when to use it versus alternatives like authenticate or connect, nor does it mention when not to use it. Given its informational nature, this is a minor gap.

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