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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does add one useful behavioral trait: 'Title discarded after the call,' which communicates statelessness/privacy. However, it does not mention the return value, whether a network request is made, failure behavior, or whether this is an existence check versus a shape validation.

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 text is extremely short and front-loaded, with no wasted words. But two sentences are not appropriately sized for a tool with seven unrelated schema parameters and no output schema; under-specification is not the same as conciseness.

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?

This definition is nearly useless for correct invocation: seven schema parameters with no connection to the stated purpose, no annotations, no output schema, and no usage context. The gap between the description and the structured fields is severe, leaving the agent unable to infer what to pass or what to expect.

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 says nothing about how to map any schema parameter to the Wikipedia title being checked. The schema lists seven parameters (ref, url, city, feed, host, json, path), none of which plausibly corresponds to a title, and their descriptions reference unrelated 'shape check' semantics. An agent cannot determine which input to supply.

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 first sentence states a specific verb and resource: 'Check whether a Wikipedia title exists.' This is a clear, recognizable purpose that differentiates it from sibling tools like normalize-url or validate-json. However, the input schema contains no 'title' parameter, so the stated purpose does not align with any actual field, leaving the tool's real scope ambiguous.

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 provides no guidance on when to use this tool versus alternatives. It neither names related tools nor gives conditions or exclusions. An agent is left to infer that this is a niche check among many shape/existence tools.

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