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

No annotations are provided, so the description must carry the full behavioral disclosure burden. The phrase 'Title is discarded after the call' hints at a read-only, stateless behavior, but it does not state whether this makes a network request, how existence is determined, what response is returned, or if any input is actually used. The minimal disclosure is insufficient for a tool with no annotation support.

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 only two sentences and front-loaded with the main action, which is concise. However, it lacks the operational mapping to the 9-parameter schema, and the second sentence ('Title discarded after the call') is not useful to an agent without context about where the title is supplied.

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?

The tool has 9 parameters, no annotations, and no output schema, yet the description gives no guidance on which parameter provides the title, no mention of return value, and no note about side effects or platform interactions. For this level of complexity, the description is completely insufficient and likely disorients an agent, making successful invocation nearly impossible.

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 schema description coverage is 100%, so the baseline is 3. The description adds no parameter-level semantics beyond the schema's own field usage hints, and it never explains how to provide the 'title' it mentions. It performs as expected only because the schema already documents each individual parameter adequately.

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 concrete check ('Check whether a Wikipedia title exists'), which is more informative than a tautology and suggests a distinct purpose from sibling tools. However, the input schema exposes nine parameters with no 'title' parameter, so an agent cannot map the stated purpose onto any available input. This makes the purpose only partially clear.

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 given about when to use this tool versus alternatives like browser-url-ok, figma-url-shape, or file-path-ok. The description does not mention usage conditions, recommendations, or exclusions, leaving the agent to guess from the ambiguous name and schema.

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