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 mentions 'Title discarded after the call,' which is a small data-retention note, but it omits any other behavioral aspects such as network access, error conditions, or side effects. For a tool with this name and purpose, the lack of detail is a significant gap.

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 extremely short (one sentence), which is concise, but it is under-specified to the point of being unhelpful. It does not front-load any essential usage details, and the brevity works against clarity given the complex, mismatched schema.

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?

Given 9 parameters, no output schema, and no annotations, the description is grossly incomplete. It fails to explain how to invoke the tool correctly, what inputs are relevant, or what the return value looks like. An agent cannot reasonably use this tool without additional external knowledge.

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 adds no parameter information whatsoever. Although the schema has 100% description coverage, the schema's parameter descriptions are entirely unrelated to the stated purpose (e.g., 'Git ref name', 'City name for a public weather hint'). The description does not compensate for this mismatch, leaving all 9 parameters without meaningful guidance.

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 clearly states the tool's purpose: 'Check whether a Wikipedia title exists.' This provides a specific verb and resource. However, it fails to connect to the actual input schema, which contains parameters like 'ref', 'url', 'city', 'feed', etc., none of which relate to a Wikipedia title. This disconnect makes the purpose ambiguous in practice, as an agent cannot infer how to supply the title.

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 gives no guidance on when to use this tool versus its many siblings (e.g., 'browser-url-ok', 'normalize-url', 'web-fetch'). There are no conditions, alternatives, or exclusions mentioned, leaving the agent without any basis for selecting this tool over others.

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