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

The phrase 'Title discarded after the call' gives a small amount of behavioral information about data retention, but it does not disclose whether the tool performs a network request, whether it is read-only, how errors are surfaced, or what side effects might occur. With no annotations, the description carries the full burden, and these behavioral traits remain undefined.

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 brief and well-structured, with the main purpose in the first sentence and an extra behavior note in the second. While it is concise, the second sentence is light on actionable detail and leaves several important execution questions unanswered.

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 9 optional inputs, missing annotations, and no output schema, the description is far too thin to be complete. It does not state what the tool returns, which parameters to pass for the title check, or how it behaves in case of missing, invalid, or unretrievable titles.

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 input schema documents all 9 parameters, so baseline credit is fair, but the description does not map the central 'Wikipedia title' input to any of the parameters. In fact, the schema contains no title field, so the description adds no parameter semantics that help the agent decide which argument should carry the title.

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 that the tool checks whether a Wikipedia title exists, using a specific verb and resource. However, it does not clarify how the title is supplied through the 9 provided parameters, leaving a gap between the stated purpose and the actual callable inputs.

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?

There is no guidance on when to use this tool instead of alternatives such as browser-url-shape, validate-json, or web-fetch. No context is given about preconditions, expected inputs, or situations where another tool would be more appropriate.

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