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

With no annotations, the description carries the transparency burden, but it only says 'Title discarded after the call,' suggesting no persistence without explaining what 'title' refers to. It does not disclose the expected result, error behavior, auth, or rate limits. The phrase adds a behavioral hint but is too vague and unconnected to the schema.

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 two sentences and front-loads the core purpose. The second sentence is concise, though its 'discarded' phrasing is ambiguous. Overall, it is appropriately sized for a simple check tool.

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?

For a tool with no output schema and no annotations, the description must explain result behavior and input mapping, but it does neither. It fails to identify which parameter carries the Wikipedia title or what the tool returns (e.g., boolean). The severe disconnect between the stated purpose and the provided schema makes the definition 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?

Although the input schema has 100% parameter descriptions, the tool description never ties 'Wikipedia title' to a specific parameter, and none of the listed properties (ref, url, city, feed, host, json, path) is obviously a title. The schema documents each field individually, but the semantic link needed to invoke this tool is missing.

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 uses a specific verb and resource: 'Check whether a Wikipedia title exists.' This distinguishes it from sibling URL/file/JSON validation tools. However, it never maps 'title' to any of the 7 input schema parameters, so the purpose is clear only at a high level.

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 siblings such as normalize-url, validate-json, or fetch-status. The second sentence about discarding the title is a behavior note, not a usage condition. An agent must infer when the tool applies.

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