add-wiki

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

The description adds behavioral context beyond annotations: it fetches sitename and API config, registers as a resource, and fails if invalid or duplicate. Annotations already indicate mutability, idempotence, and open world, so the description adds useful specifics without contradiction.

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?

Two sentences, front-loaded with the core action, no extraneous information. Every sentence earns its place.

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 the single parameter, annotations present, and no output schema, the description covers purpose, usage, and failure modes. It explains the result (selectable via set-wiki) and is fully adequate for correct invocation.

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 single parameter wikiUrl is described in schema and the description adds that it can be any page URL, not just API endpoint. With 100% schema coverage, the description adds meaning beyond the schema.

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 action (registers a new wiki as an MCP resource) and the resource (wiki), specifying it fetches sitename and API config from any URL. It distinguishes from siblings like remove-wiki and set-wiki by explaining the result.

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 explains when to use the tool (to register a new wiki) and failure conditions (not a MediaWiki wiki or already registered). It could be improved by explicitly stating when not to use it or mentioning alternatives like remove-wiki, but the context is clear.

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