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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so restating 'Read-only' is redundant. The description nonetheless adds value beyond annotations by stating it takes no input, works on every plan, and enumerating the returned fields (filing method, local/remote fit, dependency ordering, step-by-step behavior).

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?

Front-loads the resource and count, then the return fields, then the usage cue. The middle sentence is a long enumeration of returned fields, dense but each item is informative; slightly wordy rather than wasteful.

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?

No output schema exists, so the description must explain return values, and it does so field by field (id, name, URL, filing mode, server-type fit, ordering, per-step actions). Combined with the plan/input notes, nothing needed to call it correctly is missing.

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?

Zero parameters, so the baseline is 4. The description reinforces this with 'takes no input' and clarifies that returned ids are the input to submit_server, tying the output to a concrete downstream parameter.

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?

States a specific verb and resource ('List every MCP directory ManyCP can file a server in (26 today)') and immediately distinguishes itself from siblings by pointing at submit_server as the consumer of its output. An agent can tell what this returns without opening the schema.

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?

Explicitly names the two situations it serves: answering 'where can I list my MCP server?' and picking directory ids for submit_server. This routes the agent to the correct downstream sibling and leaves little to inference.

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