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 description does not need to repeat safety properties. It adds useful context about what data is returned, but it does not disclose any additional behavioral traits like rate limits, system side effects, or the format of the response. Given the annotations cover the main expectations, this is adequate but not rich.

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, well-structured sentence that leads with the action and then enumerates the key components of the returned state. There is zero wasted wording, and the information is front-loaded. It perfectly balances brevity with informativeness.

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 parameters, no output schema, read-only), the description covers all essential aspects: what it returns and the granularity of the information. It does not include details on pagination, error handling, or unavailable data, but these are not critical for a status/state retrieval tool. The coverage is complete enough for an agent to invoke it correctly and understand the response.

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 schema coverage is 100% vacuously, and the description successfully focuses on the output semantics. It describes what the tool returns in enough detail that an agent can infer the shape of the data (installed MCPs, their status, connected accounts, catalog tool counts) without needing an output schema. This exceeds the baseline for parameterless tools.

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 with explicit details (installed MCPs, connection status, accounts, catalog tool counts). The verb 'returns' and resource 'current toolkit state' are specific, and it distinguishes itself from sibling action tools like authenticate/connect and even show_version by listing the exact data returned.

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?

There is no guidance on when to use this tool versus alternatives like show_version or how it fits into a workflow. While its purpose is clear, the description does not mention when it is appropriate to call or any prerequisites. This is a notable gap given the presence of multiple information-oriented sibling tools.

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