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

Annotations mark it as a non-idempotent, open-world write; the description goes well beyond that by disclosing what files are read, what is written and returned (listing, warnings, per-directory plan), the duplicate-add failure mode, and the billing requirement. It also clarifies the tool does not publish, which meaningfully bounds the side effect.

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?

It is front-loaded with the core action and then layers in mechanics, exclusions, and requirements, with every sentence carrying information. It is dense as a single block, so slightly less scannable than an ideally structured definition, but not padded.

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?

Even with no output schema, the description summarizes the return payload, the non-submission boundary, the error case, and the prerequisites. An agent has everything needed to invoke this correctly and act on the result.

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?

Only one parameter with 100% schema description coverage, so the schema already documents repo_url and its accepted formats. The description reinforces that the repository is public but adds no format or validation detail beyond the schema, making 3 the correct baseline.

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 states a specific verb (add) and resource (an MCP server) plus the exact source (public GitHub repo), and it enumerates what ManyCP derives from the repo. It is clearly distinguishable from siblings like update_listing and submit_server, which it names.

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?

It explicitly delimits scope ('It does not submit anywhere') and provides the follow-up workflow: review the listing, fix with update_listing, then call submit_server. It also states preconditions (launch credit, Starter/Pro plan) and the duplicate-repo error condition, so an agent knows when not to call it as well.

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