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

With no annotations provided, the description carries the transparency burden. It discloses that the title is discarded and the operation is only an existence check, implying a read-only, non-persistent behavior, but it omits output format, error behavior, and network dependency.

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 short and front-loaded, with no filler. It loses a point because the second sentence adds a behavioral detail about a non-existent title parameter, making it slightly confusing despite being concise.

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 nine parameters, no output schema, and no annotations, the description is far from complete. It defines neither the expected output nor how the parameters relate to the tool purpose, so the tool cannot be invoked correctly from this definition alone.

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?

None of the nine schema parameters corresponds to a Wikipedia title, and the description provides no mapping from 'title' to any input. The schema descriptions are unrelated to Wikipedia title checking, so a caller cannot determine how to supply the title.

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 clear action and resource: checking whether a Wikipedia title exists, which distinguishes it from URL/status/validation siblings. However, the input schema contains no 'title' parameter, so the purpose statement is not fully actionable.

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?

The description gives no explicit guidance on when to choose this tool over siblings such as fetch-status or normalize-url, and no when-not-to-use conditions. The only implied usage is the verb phrase itself, which is not enough for routing.

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