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

With no annotations present, the description carries the full burden of behavioral disclosure. It does add one behavioral note—'Title discarded after the call'—which is useful for confidentiality, but it does not mention return behavior, errors, side effects, or any other invocation-relevant traits. The description is therefore minimally transparent.

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 compact and front-loaded: the purpose appears in the first sentence, and the data-discard note is a single short second sentence. It is appropriately brief for a simple check tool, though the second sentence could be more actionable if it clarified the relevant input.

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 a large 12-parameter schema and no output schema, the description is far from complete. It explains the tool's general purpose but does not clarify which parameter is the title, what the return value looks like, or whether the check is case-sensitive or Wikipedia-format-specific. An agent would struggle to invoke this tool correctly based solely on the 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?

The input schema is fully self-describing for each property, so the baseline is 3. However, the description refers to a 'Wikipedia title' while the schema exposes 12 unrelated string parameters such as ref, url, city, feed, host, json, and path, and none of them is named 'title'. This mismatch means the description adds no meaningful parameter guidance and may actively confuse an agent trying to decide which parameter to populate.

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 the core action: 'Check whether a Wikipedia title exists.' It identifies a specific verb and resource, and the Wikipedia-title domain distinguishes it from sibling tools like file-path-ok or browser-url-ok. However, it does not explicitly call out sibling differentiation or explain why this tool exists alongside similar 'ok' checkers.

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 usage guidance is provided: the description does not say when to choose this tool over alternatives, what conditions are required, or what inputs must be supplied. The only implied usage is 'if you need to check a Wikipedia title,' but there is no explicit when-to-use or when-not-to-use instruction.

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