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

No annotations are provided, so the description carries the full burden of explaining effects and expectations. The only behavioral detail is 'Title discarded after the call', which conveys some data‑retention policy. But the description says nothing about whether the call is read‑only, whether it performs network access, what happens on a missing title, whether it validates formatting, or what a 'returned' result means. The minimal evidence—'discarded after the call'—is a thin disclosure for a tool that may access external resources.

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 very short, which is easy to parse and front-loads the main purpose in its first clause. The second sentence, 'Title discarded after the call.', is a justified piece of behavioral information that earns its place by revealing important data handling. The text is not bloated, but the brevity walks a tight line between convenient and under-specified. Still, for sheer conciseness, it is efficient.

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 a nine-parameter, no-output-schema tool with no annotations, the description is far too thin. It does not explain which property to provide as the title, what the tool does with each of the nine parameters, how to recognize a valid vs. missing title, or what a result looks like. An agent reading this definition would not know how to construct a correct request. The gap between the tool's declared action and the parameter list makes the definition structurally incomplete.

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?

Although the schema descriptions cover 100% of the parameters, the tool's explicit purpose is to check a Wikipedia title, and none of the nine properties (ref, url, city, feed, host, json, path, zone, query) is documented as 'title' or even as something that maps to a Wikipedia title. The interface claims the title is discarded, but there is no way for an agent to infer which parameter carries the title value. The description adds no meaning beyond the schema and actually incurs an inconsistency: the tool claims to handle a title that the schema does not define.

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 short description clearly states the tool's purpose: checking whether a Wikipedia title exists. The phrase 'Check whether a Wikipedia title exists' uses a specific verb and resource, making the core intent unambiguous. However, it does not differentiate between sibling tools like browser-url-ok or figma-url-shape, so the tool is distinguishable only by its name and narrow focus rather than by explicit scoping statements.

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 exactly one opening sentence and the note that the title is discarded. It provides no indication of when to use this tool over a sibling, what inputs are required, or what context is appropriate. There is no guidance on prerequisites, where the title parameter should come from, or when a different checker would be more suitable. This is a clear gap for a tool with nine parameters.

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