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

There are no annotations, so the description carries the behavioral burden. It does disclose that the title is discarded after the call, which signals a stateless read operation, but it does not describe output, network behavior, errors, or any other side effects.

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 two short sentences and front-loads the core operation. The second sentence adds a useful data-handling note with little waste, though it could be integrated more cleanly.

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 large heterogeneous schema and lack of annotations and output schema, the description is not sufficient to invoke the tool correctly. It omits which parameter is the title, what response shape indicates existence, and why the other parameters are present.

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 cover all parameters, so the baseline would be 3, but the description refers to a 'title' that does not appear anywhere in the input schema. It does not map the required title to a property and actually misleads an agent into looking for a title parameter among seven unrelated fields.

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 operation: checking whether a Wikipedia title exists, with a specific resource and verb. It is not a tautology and distinguishes this from nearby validation tools, though it does not name any sibling alternative.

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 for when to use this tool instead of siblings such as fetch-status, validate-json, or normalize-url. The description offers no selection conditions, prerequisites, or exclusions, so an agent must infer usage from the name alone.

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