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

With empty annotations, the description carries full responsibility for disclosing behavior. It does disclose that the title is 'discarded after the call,' which is a useful data-handling note. But it does not explain whether the call is a network request, whether it is read-only, how results are returned, or what side effects might occur.

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 extremely short and contains no filler. The sentence about discarding the title is a meaningful behavioral note rather than repetition. It is inefficiently minimal in coverage, but it is not wordy or poorly structured.

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?

This tool has 7 parameters, no annotations, and no output schema, so the description alone must provide enough context to invoke it correctly. It fails to do so: there is no mapping from parameters to the title, no expected return value, and no explanation of how existence is verified. An agent would not reliably know what input to provide or what result to expect.

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 description adds no meaning to the input schema. The schema exposes seven unrelated-looking parameters like ref, url, city, feed, host, json, and path, but none is identified as the Wikipedia title. Even though each parameter has a schema description, those descriptions do not align with the tool's stated purpose, leaving an agent unable to determine which parameter to pass.

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 clear verb and resource: 'Check whether a Wikipedia title exists.' This distinguishes the tool from URL-focused siblings like normalize-url or browser-url-ok. However, the clarity is undermined by the input schema, which contains no 'title' parameter, so the stated purpose does not map cleanly onto the tool's actual inputs.

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?

There is no guidance about when to use this tool versus alternatives such as citation, normalize-url, or fetch-status. The description implies it is for Wikipedia title existence checks, but it does not state any exclusions, prerequisites, or conditions for choosing a sibling tool instead.

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