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

The line 'Title discarded after the call' is an attempt at data-handling transparency, but with no annotations the description must carry more weight. It never says what the result is, whether a network lookup occurs, or what failure/absence means, so the behavior is under-described.

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, with no wasted words, so it is concise. However, the second sentence says only 'Title discarded after the call' and does not earn the deiconstrued in strictly useful meaning; it introduces a term not present in the schema.

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?

With nine optional parameters, no output schema, and no annotations, the description is far too thin for an agent to invoke the tool correctly. It does not say which blob should contain the Wikipedia title, how success is returned, or what 'discarded' does in about what the tool returns.

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 contains nine optional string fields but no 'title' property. The description refers to a 'Wikipedia title' and says it is discarded, but gives no mapping from that concept to any schema property, leaving the agent without a correct parameter to populate. This is misleading when paired with the schema.

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 ('Check whether a Wikipedia title exists') and names a distinct resource ('Wikipedia title'), which makes the tool's intent clear. It does not explicitly contrast with sibling validators, but the resource is enough to separate it from file/URL/domain checks.

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 about when to use this tool versus the many sibling shape/check tools, and no explicit 'when not to use'. The description only implies its use for testing title existence, without saying how that differs from URL validation or generic lookup tools.

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