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

The description notes that the title is discarded after the call, but this is the only behavioral disclosure. No annotations are present, so the description carries full burden; it fails to explain the tool's side effects, the purpose of the nine unrelated parameters, or any other behavioral traits. The statement about discarding a title is confusing because no title parameter exists.

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 sentence and thus concise, but it lacks essential information. The brevity is not well-structured because it omits critical context about the parameters and behavior, making it under-specified rather than appropriately concise.

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 nine parameters and no output schema, the description is grossly incomplete. It does not explain what the tool does with any of the parameters, nor does it reconcile the stated purpose (Wikipedia title check) with the unrelated schema fields. An agent cannot correctly invoke this tool based on the description alone.

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 does not mention any of the nine parameters, and the schema descriptions are generic and mismatched to the stated purpose (e.g., 'ref' as a Git ref name, 'city' as a weather hint). Schema coverage is 100%, so the baseline is 3, but the description adds no value in connecting parameters to the tool's function, leaving the agent confused about how to invoke it.

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 verb and resource: 'Check whether a Wikipedia title exists.' It is clear on its face but does not distinguish from siblings like browser-url-ok or file-path-ok, and the parameter schema is entirely unrelated to the stated purpose, creating ambiguity about what the tool actually does.

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 provided on when to use this tool versus alternatives. The description is a single sentence with no mention of context, exclusions, or alternative tools among the many sibling validation tools.

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