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

The only behavioral disclosure is 'Title discarded after the call,' which addresses data retention but not other important behaviors such as network access, error handling, or how the title is resolved against Wikipedia. Because there are no annotations, the description carries the full burden and does not provide enough behavioral context for safe invocation.

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 concise: two short sentences with no filler. The purpose is front-loaded and the 'discarded after the call' note adds a behavioral detail without wasting words. It is appropriately sized, though slightly under-specified.

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?

The output schema documents the return shape, but the description still fails to explain which input field carries the Wikipedia title and gives no context about expected inputs, examples, or failure behavior. Given the mismatched parameter set, an agent is unlikely to call this tool correctly without additional information.

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 input schema has descriptions for all seven parameters, but none of them is a 'title' parameter and none is explained as the Wikipedia title to check. The description does not map 'title' to any schema field, so an agent cannot determine which parameter to populate. Schema coverage is high, but the connection to the described purpose is missing.

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 purpose: 'Check whether a Wikipedia title exists.' This is a specific verb and resource, but it is not backed by the input schema, which exposes unrelated parameters like ref, city, feed, host, and json. The purpose is understandable on its own, but the schema mismatch makes the tool hard to identify as the correct one for a title check.

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 alternatives like normalize-url, browser-url-ok, or citation. The description only says what the tool does, not when it should be preferred or avoided. No exclusions or alternative conditions are provided.

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