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

The description discloses one useful behavioral trait: 'Title discarded after the call.' This indicates the input is not retained, which is valuable privacy-relevant information. However, with no annotations present, the description still omits other relevant behaviors such as read-only status, network dependence, rate limits, or return shape.

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 a single, front-loaded sentence with no filler words. Both clauses contribute information: the tool's operation and the discard behavior.

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?

This tool is nearly impossible to invoke correctly from the description alone: there is no title parameter, no return value description, and no output schema. The schema contains seven unrelated-looking parameters, and the description fails to explain how any of them relate to the stated purpose.

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 schema provides descriptions for all seven parameters, but those descriptions are unrelated to the stated purpose: none reference a Wikipedia title. The description adds no mapping between its 'title' concept and any schema property, and instead creates confusion by mentioning a title that does not exist among the parameters.

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 clearly states a specific verb and resource: 'Check whether a Wikipedia title exists.' It is not a tautology and seems distinct from sibling tools like browser-url-ok or web-fetch. However, no parameter is identified as carrying the title, so the stated purpose is not fully actionable from the description alone.

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 no guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. The only implied usage is when one needs to verify a Wikipedia title, but no context is provided about choosing this over web-fetch or browser-url-ok.

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