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

No annotations are present, so the description must carry the full burden of behavioral disclosure. It does reveal that the title is discarded, but it does not explain what the tool returns, what happens on failure, or whether any network request is made to Wikipedia.

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 no fluff, which is good, but it is too terse for a seven-parameter tool with no annotations. The second sentence adds a behavioral detail, but the overall terseness leaves critical invocation details missing.

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 lack of annotations, the absence of an output schema, and an input schema that does not align with the description, this definition is not complete enough for an agent to use confidently. It fails to explain which input carries the Wikipedia title or what the success/failure response looks like.

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 documents seven unrelated parameters, none of which is named 'title', while the description repeatedly refers to a title being checked and discarded. This mismatch means the description does not help an agent map its stated input to any actual parameter, undermining correct invocation despite the schema having per-field descriptions.

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 operation: checking whether a Wikipedia title exists, which distinguishes it from sibling shape/URL/JSON tools. However, the input schema has no 'title' parameter, which creates ambiguity about how the caller supplies the actual title.

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 choose this tool over alternatives or when not to use it. The purpose can be inferred, but no explicit context, prerequisites, or exclusions are provided.

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