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

No annotations are present, so the description carries the full burden. It does disclose a meaningful lifecycle trait ('Title discarded after the call') and implies a read-only existence check. However, it omits the output format, whether a network request is made, or failure behavior, leaving transparency only partial.

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?

Two short sentences, no filler, and the core purpose is front-loaded. The second sentence adds a useful lifecycle detail without bloat. This is as concise as a description can be.

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 seven parameters, no annotations, and no output schema, the tool is deeply under-specified. The description does not say which parameter holds the Wikipedia title, what the tool returns, or any constraints. An agent cannot reliably invoke the tool based on 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?

The schema fully describes seven parameters, but none is a Wikipedia title—they are ref, url, city, feed, host, json, and path. The description adds no mapping between 'title' and any property, and the only mention of 'title' is the discard note. High schema coverage cannot compensate for this critical mismatch, which prevents correct invocation.

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 verb and resource: 'Check whether a Wikipedia title exists.' This is unambiguous and distinguishes this tool from sibling shape-checkers by the unique subject matter. The absence of a title parameter in the schema slightly clouds practical use, but the stated purpose itself is crystal clear.

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 for when to use this tool over the many sibling checkers (e.g., domain-shape, github-repo-shape). The 'Title discarded after the call' note is a behavioral detail, not a usage guideline. An agent is left entirely to infer context from the tool name and description.

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