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 agent knows this is a safe read operation. The description adds detail about what state is returned (installed MCPs, connection status, accounts, catalog tool counts). However, it does not describe any caveats like partial states or performance implications, which is acceptable for a simple read-only tool with strong annotations. The description supplements but doesn't over-explain.

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: 'Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.' It conveys all relevant information without any filler, perfectly concise and 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?

With no parameters and no output schema, the description covers the key elements returned and implies it's a read-only state snapshot. It doesn't describe the exact structure or potential error states, but for a simple information tool, it's sufficiently complete. Sibling tools like connect or authenticate suggest context, and this tool likely serves as an overview, which is adequately described.

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 input schema provides no information to enhance. The description effectively explains the return content, which is the only meaningful semantic information for a parameterless tool. Baseline of 4 is appropriate given no parameters require documentation.

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 function: 'Returns the current toolkit state' with specific elements listed (installed MCPs, connection status, accounts, catalog tool counts). This is specific enough to distinguish from sibling tools like 'show_version' or 'toolkit_info' isn't ambiguous. It lacks a comparative statement with siblings, but the verb and resource scope are clear.

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?

No information about when to use this tool versus others, no prerequisites, and no mention of context like needing to connect first. Sibling tools like 'connect' and 'authenticate' might be relevant but are not referenced. This is a bare functional description without usage guidance.

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