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

With no annotations, the description must carry the burden of disclosing side effects. 'Title discarded after the call' hints at no persistence, but it does not explicitly state that the tool is read-only, nor does it mention any side effects beyond discarding. The description is too minimal to provide meaningful transparency.

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 brief and to the point, but it omits essential information such as which parameter is the title and what the return value indicates. Brevity alone does not make it concise; it is under-specified and lacks a clear structure to guide usage.

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 tool's apparent purpose (checking Wikipedia title existence), the description fails to explain how to provide the title, what constitutes a valid request, or what the output means (e.g., boolean, error codes). The mismatched schema and lack of output documentation make the tool nearly unusable without additional context.

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 parameter schema descriptions are misleading and disconnected from the tool's purpose. For example, 'ref' is described as a 'Git ref name' and 'city' as a 'City name for a public weather hint', which have no relation to checking a Wikipedia title. The descriptions actively confuse rather than clarify, providing negative value.

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-object pair ('Check whether a Wikipedia title exists'), but it fails to identify which of the 9 parameters corresponds to the title. The parameter schema includes unrelated fields like 'ref', 'url', 'city', and 'query', making the purpose ambiguous and difficult to act on.

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?

No guidance is provided on when to use this tool versus the many sibling tools (e.g., search-query-len, normalize-url, validate-json). The description does not mention any context, prerequisites, or alternative tools, leaving the agent without decision support.

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