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

Annotations already declare readOnlyHint=true and idempotentHint=true, indicating a safe read operation. The description adds valuable behavioral context by detailing the exact contents of the returned state (MCPs, statuses, accounts, counts), going beyond the generic 'read' label. It doesn't cover edge cases like rate limits or auth, but those are less critical for an annotation-backed read-only 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?

The description is a single, front-loaded sentence that immediately states the purpose and uses a colon-enumerated list to convey the output fields efficiently. Every word adds value, with no fluff or repetition.

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 zero-parameter, read-only introspection tool, the description is complete: it fully explains what the tool returns (installed MCPs, connection status, accounts, catalog counts). No output schema exists, but the description covers the return shape sufficiently, and given the strong annotations, no additional context is essential.

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 empty schema fully covers parameter semantics. Per rubric guidelines, 0-parameter tools receive a baseline score of 4 because no compensation is required; the description doesn't need to explain parameters that don't exist.

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 the clear verb 'Returns' with a specific resource, 'the current toolkit state,' and enumerates exactly what that includes (installed MCPs, connection status, connected accounts, catalog tool counts). This level of specificity makes the tool's purpose unmistakable and distinguishes it from siblings like show_version.

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 when to use the tool (to inspect toolkit state) but provides no explicit guidance on alternatives, exclusions, or when not to use it. It leaves the use case to inference rather than directly stating it.

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