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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions 'Title discarded after the call,' which is a minor data-handling note, but it does not describe what the tool actually does with the other parameters, what it returns, or any side effects. The behavior is largely unexplained, especially given the mismatch between the purpose and 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 extremely short (one sentence), but this is under-specification rather than effective conciseness. It does not provide necessary information, and the single sentence does not earn its place by clarifying purpose or usage.

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 9 optional parameters, no required fields, no output schema, and no annotations, the description is drastically insufficient. It fails to explain the tool's overall behavior, how to invoke it correctly, or what response to expect. The tool appears to be a generic utility with mismatched documentation.

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 each parameter is documented individually. However, the tool description adds no meaning beyond the schema; it does not explain how parameters like 'ref', 'url', or 'city' relate to checking a Wikipedia title. The description is even misleading because it implies a title input that does not exist in the schema.

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 action ('Check whether a Wikipedia title exists') but fails to connect it to any of the 9 input parameters, none of which are named 'title'. This creates ambiguity about which parameter corresponds to the title. It also does not differentiate from sibling tools like 'browser-url-ok' or 'fetch-status', which might also check URL/title availability.

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. There is no mention of context, prerequisites, or exclusions. The single sentence gives no indication of when this tool is appropriate.

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