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

With no annotations, the description must disclose side effects and behavior. It only says the title is 'discarded after the call,' but does not mention whether the tool performs a network request, whether it is read-only, or what happens on failure.

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 concise and front-loaded, with no unnecessary wording. However, it is too terse for a tool with nine unrelated parameters and includes a confusing second sentence about discarding the title.

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 description and schema together do not explain what parameters are relevant, what the return value looks like, or what 'exists' means. The lack of an output schema and the unrelated parameter descriptions make the tool incomplete for an agent to use correctly.

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 descriptions are all present but unrelated to Wikipedia title checking. The description does not map the concept of 'title' to any parameter, and none of the nine optional parameters is clearly the title, so the parameter semantics are confusing and unusable.

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 a specific action: checking whether a Wikipedia title exists. However, the input schema contains no 'title' parameter and includes many unrelated optional fields, so the clarity is undermined by the mismatch.

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 any of the sibling tools. It also implies a 'title' input that the schema does not provide, which could mislead an agent into using it incorrectly.

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