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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'Title discarded after the call,' which is irrelevant to the actual parameters and does not clarify side effects, error behavior, or read-only nature. It gives no meaningful transparency.

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 a single sentence, which is concise, but it is under-specified and not front-loaded with the most useful information. It lacks structure and any detail that would help an agent use the tool correctly.

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?

For a tool with 9 diverse parameters and no output schema, the description is grossly inadequate. It does not explain how to invoke the tool for any parameter, what the expected behavior is, or how it relates to its purpose.

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?

Although the schema covers 100% of parameters, the description adds no value to parameter understanding. It mentions a 'Wikipedia title' that does not exist as a parameter, so it neither clarifies nor compensates for the schema's meaning.

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 action (check existence) and resource (Wikipedia title), but no parameter in the schema corresponds to a title, making the purpose ambiguous and disconnected from the tool's actual inputs. It does not distinguish it from sibling shape-check tools.

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 provided on when to use this tool versus the many sibling shape-check tools (e.g., browser-url-ok, file-path-ok). There is no mention of prerequisites, exclusions, or alternative selection criteria.

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