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

The description adds one behavioral note: 'Title discarded after the call.' This indicates ephemeral handling, which is useful. But annotations are all false, so they provide no safety or side-effect hints. The description does not disclose whether the check is performed over the network, whether it returns a boolean, or what 'exists' means. It adds some value but leaves much unsaid.

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 only two short sentences with the main purpose front-loaded and no filler words. It is appropriately concise for the amount of content it carries. It loses a point because it is so sparse that important context is missing, but that is more a completeness issue than a conciseness issue.

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?

With no output schema and all-false annotations, the description must carry the full explanatory burden. It fails to specify how to supply the title, what the result looks like, or what 'exists' means operationally. The tool has 8 parameters and no guidance about which one is relevant, making the definition incomplete for an agent to call it correctly.

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 schema descriptions cover all eight parameters, so the baseline schema burden is high. However, the tool description makes no attempt to map its 'Wikipedia title' concept to any parameter, and the parameter names/descriptions (e.g., 'HTTPS URL to normalize or cite', 'Git ref name') do not suggest a title input. This actively confuses parameter selection rather than adding meaning.

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 and resource: 'Check whether a Wikipedia title exists.' That is clear in isolation. However, the input schema has no 'title' parameter – it contains ref, url, city, feeed, host, json, path, and v – so the description does not connect to the actual tool invocation. It also doesn't differentiate from sibling validators such as browser-url-ok or playwright-url-ok beyond the word 'Wikipedia'.

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 gives no guidance about when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or scenarios where another tool would be more appropriate. The only implicit hint is that it involves Wikipedia titles, but no explicit usage context is provided.

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