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

Annotations contain only the non-standard "function": false, so the description must carry the behavioral disclosure burden. The single claim 'Title discarded after the call' weakly implies statelessness, but it does not say whether this is a read-only network operation, whether permissions are needed, whether any side effects occur, or how 'exists' is evaluated.

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 sentences, but the first is near-tautological and the second is cryptic and contradictory. Brevity is not a virtue when it omits the essential mapping of title to an input parameter; the content does not earn the space it uses.

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 eight parameters, no output schema, and no useful annotations, this description is completely inadequate. There is no mention of which parameter carries the title, what the success/failure response looks like, or any error behavior. An agent would be unable to construct a correct invocation from this definition.

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?

All eight schema parameters have individual descriptions, so the baseline is 3, but the tool description adds no value and instead introduces a phantom 'title' parameter that does not exist in the schema. This actively makes parameter understanding harder rather than supplementing the schema.

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 says 'Check whether a Wikipedia title exists,' which restates the tool name and adds only the bland verb 'check.' It never connects to the input schema: none of the eight parameters (ref, url, city, feed, host, json, path) is 'title,' so an agent cannot tell what to supply. The phrase 'Title discarded after the call' further muddles the purpose.

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 siblings like normalize-url, validate-json, or domain-shape. No conditions, prerequisites, or alternatives are mentioned; the only implied use is a vague 'check Wikipedia title exists' with no explanation of how that maps to the provided inputs.

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