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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotenceHint=true. The description adds a small behavioral detail—'Title discarded after the call'—which conveys a privacy/retention trait beyond the annotations. It does not, however, disclose the return format, network usage, or any rate-limit implications. This is adequate but not rich.

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 front-loaded: the purpose is in the first clause, and the second sentence adds a behavioral note. Every sentence earns its place with no fluff. It is under-specified, but that is a completeness issue, not a conciseness flaw.

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?

The tool is simple in concept, but the description leaves critical gaps: it does not state which schema parameter represents the Wikipedia title, what the tool returns (e.g., boolean, status code), or how this differs from sibling existence checks. There is no output schema to compensate, and the annotations are generic. An agent cannot reliably construct a valid call from this description alone.

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?

While the schema provides a description for every property, those descriptions are generic and misaligned with the tool's stated purpose—e.g., path is described as 'File path to check' and url/feed/city/host/json/ref have unrelated meanings. The tool description adds no mapping from the Wikipedia title to any parameter, and the schema itself contains a duplicate 'path' key. With no 'title' property and no clarification, an agent cannot determine what input to provide.

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.' This is clear and matches the tool name. However, it does not explicitly differentiate from sibling existence-check tools like file-path-ok or browser-url-ok, and it never identifies which schema parameter actually holds the title, creating ambiguity for the agent.

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 when-to-use guidance is provided. The description does not mention alternatives, exclusions, or conditions for selecting this tool over similarly named existence-check siblings. The 'Title discarded after the call' note hints at statelessness but does not help the agent decide when to invoke the tool.

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