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 behavioral disclosure. It does mention that the title is 'discarded after the call', which hints at statelessness, but it does not disclose whether this is a network/read-only operation, what it returns, how failures are handled, or whether normalization is applied. The retention note is also confusing because no 'title' parameter appears in the schema.

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 and front-loads the purpose in the first sentence. The second sentence adds one behavioral note. It is appropriately concise, though the brevity comes at the cost of missing essential input and return information.

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?

For a tool with a seven-property input schema and no output schema, the description is severely incomplete. It does not say which parameter carries the Wikipedia title, what the success/failure response looks like, whether it performs a live Wikipedia lookup, or what errors occur. An agent cannot correctly select or invoke this tool based on the provided 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?

The description references a 'title' input, but the input schema contains no 'title' property; it instead lists ref, url, city, feed, host, json, and path. The description provides no mapping from these schema properties to the intended title check, so an agent cannot determine what to pass. This is a critical semantic gap and actively misleading.

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 operation: 'Check whether a Wikipedia title exists.' This is a clear verb-resource pairing and broadly distinguishes the tool from URL/shape/file validators. However, it does not explicitly differentiate it from sibling tools like web-fetch or normalize-url, which might also be relevant for Wikipedia lookup tasks.

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 about when to use this tool versus alternatives, nor any exclusions or prerequisites. The intended use is only implied by the phrase 'Check whether a Wikipedia title exists', but the description never says 'use this when you need to verify page existence without fetching content' or mentions what inputs it expects.

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