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

The description explicitly says 'Returns', indicating a read-only operation, which aligns with annotations (readOnlyHint: true, idempotentHint: true). There is no indication of side effects, and the nature of the tool (status query) makes behavior fully transparent.

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 uses a colon to introduce a clear list of outputs. It is concise without sacrificing essential details, achieving an optimal balance.

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 description lists the specific information returned, which is quite complete for a read-only status tool. However, it does not provide an output schema or detail how the results are structured (e.g., as a list or object). Given the sibling tools, additional context on how this tool integrates (e.g., complements 'show_version') would enhance completeness.

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, and the schema is empty with 100% description coverage. The description accurately reflects that no inputs are required, so parameter semantics are not applicable and are handled perfectly.

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 specific elements (installed MCPs, connection status, accounts, catalog tool counts). This leaves no ambiguity about the tool's function.

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 a read-only status overview tool but does not explicitly state when to use it (e.g., before connecting or for troubleshooting). However, its purpose is self-evident, and sibling tools like 'connect' and 'show_version' provide context. A brief note on typical usage would improve it.

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