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

The description discloses one behavioral trait ('Title discarded after the call'), but there are no annotations to provide a safety baseline. It omits crucial details such as network behavior, exact match semantics, or potential side effects. The claim about a 'title' is also disconnected from the actual schema, making the disclosure difficult to act on.

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 and front-loads the primary purpose in the first sentence. However, the brevity borders on under-specification, and the second sentence's 'discarded' detail does not compensate for the lack of parameter guidance.

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?

The description and schema together cannot support a correct invocation: the tool is about checking a Wikipedia title, yet no parameter exists to receive that title. With no output schema and no annotations, the information is fundamentally incomplete.

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 explain how to supply the Wikipedia title, and the input schema contains no 'title' property — only unrelated fields like ref, url, city, feed, host, json, and path. The schema descriptions are self-contained but irrelevant to the tool's stated purpose. This is a severe mismatch that leaves the agent unable to call the tool correctly.

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 opens with a specific verb and resource: 'Check whether a Wikipedia title exists.' This clearly states what the tool does. However, it does not explicitly distinguish itself from sibling tools with similar shape-check behavior, lowering it from a 5.

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 about when to use this tool versus alternatives. The description does not mention any conditions, exclusions, or trade-offs that would help an agent choose between this and sibling tools like 'domain-shape' or 'normalize-url'.

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