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

Annotations already declare readOnlyHint=true, openWorldHint=false, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe, non-mutating read. The description adds the exact scope of what the tool reports (current state) but nothing about latency, freshness, or potential failures, which is acceptable for a simple info-gathering tool with strong annotation coverage.

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 sentence, direct, and front-loaded with the verb 'Returns' and the resource 'current toolkit state'. It efficiently lists the key data points without extraneous words.

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?

The tool is simple (no params, no output schema) and annotations provide safety coverage. The description sufficiently explains what the return value contains. Missing details like the exact format of output could be a minor gap, but given the complexity, it is complete for the intended use.

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?

With zero parameters, the input schema is trivially documented (100% coverage). The description adds value by explaining what the tool returns, which is the semantic content an agent needs to interpret the output. Since there are no parameters to describe, a baseline of 4 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 clearly states the tool returns the current toolkit state and enumerates the specific pieces of information it provides (installed MCPs, connection status, accounts, catalog tool counts). This is specific and distinct from siblings like authenticate or show_version, which have different purposes.

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 it should be used when you need an overview of the toolkit's state registry, which serves as a good context for when to call it. It does not explicitly mention alternatives or when not to use it, but with zero parameters and a clear purpose, this is adequate.

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