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

There are no annotations, so the description carries full responsibility. It states 'Title discarded after the call,' implying a stateless operation, but fails to clarify what 'title' refers to since there is no 'title' parameter in the schema. It also does not disclose network usage, error behavior, or how the many unrelated parameters are handled, which is a significant transparency gap.

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 short sentence, which is concise but severely under-specified. It does not convey the necessary context for a tool with nine optional parameters and no annotations. The brevity here is under-specification, not efficient conciseness.

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's complexity (9 parameters, no annotations, no output schema), the description is woefully incomplete. It does not explain the relationship between the parameters and the title check, nor does it describe return values, side effects, or typical use cases. An agent cannot correctly invoke this tool based on the provided 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?

Although schema coverage is 100%, each parameter's description is generic and unrelated to the tool's purpose (e.g., 'City name for a public weather hint' has nothing to do with Wikipedia). The tool description adds no parameter-specific meaning and does not compensate for the misleading schema. The parameters appear to be placeholders rather than meaningful inputs for title checking.

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 action ('Check whether a Wikipedia title exists') with a clear resource (Wikipedia title). It is not a tautology and is distinguishable from siblings by its focus on Wikipedia title existence. However, it does not explicitly differentiate from similar tools like 'browser-url-ok' or 'normalize-url', and the schema's unrelated parameters introduce confusion.

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 does not mention prerequisites, conditions, or exclusions. An agent has no indication of when this tool is preferred over siblings like 'wiki' or 'url-ok' tools.

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