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

No annotations are provided, so the description must fully disclose behavior. It only states that the 'Title discarded after the call', implying no persistent side effects, but does not clarify whether the check involves network access, what happens on invalid titles, or any other behavioral details. The description is too sparse to convey the tool's operation.

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 concise—two short sentences with no fluff. It front-loads the primary action ('Check whether a Wikipedia title exists') and then adds a note about discarding. For its length, it is well-structured, but the brevity comes at the cost of substance.

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 9 parameters, no required fields, and no output schema, the description is far from complete. It does not explain how the parameters are used, what the tool returns (e.g., boolean, status), or any edge cases. An agent cannot confidently call this tool correctly based on the description alone. The mismatch between the description and schema compounds the incompleteness.

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 coverage is 100%, so the schema documents each parameter. However, the description adds no meaning to the parameters—it does not explain how 'ref', 'url', 'city', etc. relate to checking a Wikipedia title. In fact, the description mentions a 'title' that does not appear in the schema, misleading the agent about the expected input. The description fails to bridge the gap between the schema and the stated purpose.

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. However, the input schema does not contain a 'title' parameter, and the parameters listed (ref, url, city, etc.) are unrelated to Wikipedia titles. This mismatch makes the purpose confusing and does not clearly differentiate from sibling tools that also perform checks (e.g., browser-url-ok, domain-shape). The action is clear in isolation but not aligned with the schema.

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, exclusions, or alternative tools. An agent would have no basis for selecting this over sibling tools like wiki-title-check or domain-shape.

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