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

No annotations are present, so the description carries the burden. It only discloses that the title is discarded, implying statelessness, but does not explain side effects, return value, or behavior on missing titles.

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 brief, but the single sentence is misleading because it references a 'title' that has no corresponding input. It does not effectively front-load essential information.

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 no output schema, no required parameters, and a severe mismatch between description and schema, the tool lacks essential context for any agent to invoke it correctly.

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?

Each parameter has a description, but none relate to a Wikipedia title. The schema parameters (ref, url, city, feed, host, json, path, zone, query) are entirely disconnected from the stated purpose, making parameter usage nonsensical.

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 stated purpose is specific ('Check whether a Wikipedia title exists'), but the input schema contains no parameter for a Wikipedia title, making the actual function ambiguous. It does not clearly distinguish from siblings because the required input is missing.

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 on when to use this tool versus any sibling tool. The only extra statement ('Title discarded after the call') is behavioral, not usage guidance.

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