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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. The only behavior mentioned is 'Title discarded after the call,' but there is no title parameter, making the statement misleading. The description does not disclose side effects, permissions, or output behavior for the actual parameters.

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, which is concise, but the brevity sacrifices essential information. It is a single sentence with no structure or explanation of how the parameters relate to the purpose. It is not tautological, but it is under-specified rather than efficiently structured.

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?

Given the tool has 9 optional parameters and no output schema, the description is severely incomplete. It does not specify which parameter to use for the title check, what the return value is, or any side effects. An agent cannot reliably invoke this tool correctly based on the description.

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?

Schema description coverage is 100%, so baseline is 3. However, the tool description adds no meaning beyond the schema and actively misleads by referencing a 'title' that does not exist. The parameter descriptions themselves are generic (e.g., 'city' for weather hint) and do not connect to the stated purpose, so the description fails to add value.

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') but the schema contains no 'title' parameter. It is unclear which input represents the title, and the description does not differentiate it from sibling shape-check tools like browser-url-ok or file-path-ok.

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 on when to use this tool versus alternatives. The description does not mention any conditions, prerequisites, or sibling tools, leaving the agent to guess its applicability.

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