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

No annotations are provided, and the description only vaguely mentions that the 'Title' is 'discarded after the call,' implying no persistence but not clarifying side effects, permissions, or failure behavior. This is insufficient for a tool with 9 parameters.

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 concise, using only two short sentences. It avoids unnecessary detail, which is good, though it sacrifices essential information.

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 the complexity of the schema (9 parameters, no required fields, no output schema), the description is severely incomplete. It does not explain how to invoke the check, what the response looks like, or how the parameters relate to the purpose.

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 does not map any of the 9 schema parameters to the 'title' it refers to. Although the schema descriptions exist, they are generic and unrelated to the tool's stated purpose, so the description adds no clarification.

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 the core action clearly ('Check whether a Wikipedia title exists'), but it does not specify which of the 9 input parameters corresponds to the title, making the purpose ambiguous in practice.

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 provided on when to use this tool versus the many sibling tools that perform similar existence checks. It does not mention alternatives, prerequisites, or typical use cases.

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