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

With no annotations, the description carries the burden of behavioral disclosure, and 'Title discarded after the call' is a useful statelessness hint. However, it does not disclose the return value, error behavior, or whether an actual network lookup is performed, and the 'title' concept never appears in 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 short sentences and front-loads the main action with a brief behavioral note. It is concise and easy to parse, though the second sentence is somewhat redundant with the repeated 'discarded' language in the schema descriptions.

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?

Even for a simple existence-check tool, the description is incomplete: it provides no mapping from the stated 'title' to any schema property, no output/return information, and no annotation coverage. An agent cannot reliably call this tool based solely on the provided definition.

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 description's core input, the Wikipedia title, is not present as a property in the input schema. The schema documents ref, url, city, feed, host, json, and path, but none is mapped to the title being checked, leaving an agent unable to determine how to invoke the tool. This is a critical semantics failure.

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 ('Check') and resource ('whether a Wikipedia title exists'), making the core purpose immediately clear. It does not distinguish from sibling tools, so it does not earn a 5. The missing 'title' parameter is a parameter-mapping problem rather than a purpose-clarity problem.

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?

'Check whether...' implies a validation/existence use case, but the description gives no explicit when-to-use or when-not-to-use guidance. It does not mention alternatives or warn against using a sibling like web-fetch or normalize-url for the same need.

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