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

With no annotations, the description carries the full burden. It discloses that the title is discarded, but does not explain return values, side effects, or any operational behavior beyond the existence check. A simple 'check' is ambiguous regarding output format or error handling.

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 two sentences are short and front-load the purpose. However, the extreme brevity omits essential usage information, crossing from conciseness into under-specification.

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, no annotations, and a schema that does not match the description, an agent has no way to correctly invoke the tool. The description fails to explain which input carries the title or what response to expect.

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 description refers to a 'title' but the schema contains no such parameter; instead there are unrelated parameters like ref, url, city, feed, host, json, and path. Schema descriptions cover all parameters, but they are irrelevant to the stated purpose, leaving the agent with no way to provide the title.

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 action ('Check') on a specific resource ('whether a Wikipedia title exists'), which is a meaningful and non-tautological statement. However, it does not differentiate from sibling tools like validate-json or browser-url-ok, and the title resource is not reflected in the schema.

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 given for when to use this tool versus alternatives. The description only states the function purpose, with no conditions, prerequisites, or explicit exclusions.

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