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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the agent knows this is a safe read operation. The description adds the specific information returned (installed MCPs, connection status, accounts, catalog tool counts), which is useful behavioral context. However, it does not detail any potential output size or if it could be slow, and it doesn't explain how 'connection status' is determined. Given strong annotations, a 3 is appropriate as the description adds some value but not exhaustive.

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, concise and front-loaded with the key function ('Returns the current toolkit state'). It includes specific details about what is contained in that state, making every word count. This is an excellent example of conciseness without losing 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 that this is a simple info tool with no parameters and no output schema, the description covers the essential aspects: what it returns and the scope (toolkit state, connections, catalog tools). It does not need to elaborate on return format since there is no output schema, but it could mention potential size or structure. However, the description is sufficiently complete for the tool's simplicity.

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, there are no parameter semantics to document, so the description is not required to explain parameters. It clearly states what is returned, which provides semantic content beyond the schema. This justifies a baseline 4 for zero-param tools as the description effectively communicates the sole purpose.

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 that the tool returns the current toolkit state and specifies what that includes (installed MCPs, connection status, accounts, catalog tool counts). This distinguishes it from siblings like authenticate, connect, and show_version. A slight deduction because it doesn't explicitly mention what the return value contains beyond a summary, but the purpose is 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?

The description implies that this is for checking the current state of the toolkit, which is a typical use case. However, it does not explicitly state when to use it as opposed to alternatives, nor does it mention any conditions under which it should not be used. Since this is likely a diagnostic/info tool, the usage context is clear enough, but no direct alternatives are named.

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