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

No annotations are provided, so the description carries the behavioral burden. It discloses one useful privacy trait: 'Title discarded after the call.' However, it does not describe return shape, failure behavior, or network dependency, so transparency is partial.

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 short and front-loaded with the tool's purpose, followed by a one-sentence behavioral note. Besides the confusing 'title' reference that is missing from the schema, the text is efficient and appropriately sized.

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 definition is not complete enough to invoke correctly: there are no annotations or output schema, and the description never maps the tool's stated purpose to any of the seven input parameters. The schema's unrelated parameters and absent title field leave a critical gap.

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 contains seven string parameters with individual descriptions, but none corresponds to a Wikipedia title. Several are explicitly marked 'discarded' or describe unrelated concepts like weather hints, Git refs, and RSS feeds. The description gives no hint how to supply the title, so an agent cannot determine a valid invocation.

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 action and resource: 'Check whether a Wikipedia title exists.' This is clear and distinct from sibling tools like domain-shape or github-repo-shape. The second sentence about discarding the title does not obscure the core purpose.

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 purpose statement implies when to use the tool: when an agent needs to confirm whether a Wikipedia title exists. However, it never explicitly states usage context, exclusions, or alternatives among the many sibling tools, so the guidance is only implied.

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