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

The description mentions 'Title discarded after the call,' but the schema contains no title parameter, making the behavioral note confusing rather than informative. No side effects, network behavior, or output semantics are disclosed.

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 the main purpose. However, the second sentence ('Title discarded after the call') is confusing because no title input exists in the schema, so it does not earn its place.

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?

The description is incomplete for the tool's complexity: it does not explain which parameter is the title, what the output represents (e.g., boolean existence flag), what error behavior occurs, or why the many unrelated 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?

Although the schema has 100% description coverage, those descriptions are generic and mismatched (e.g., 'Git ref name,' 'IANA timezone name'), none of which clearly relate to checking a Wikipedia title. The tool description adds no meaningful parameter semantics and fails to identify which field should receive 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 states a concrete action: 'Check whether a Wikipedia title exists.' This distinguishes it from many sibling tools, but no 'title' parameter appears in the input schema, so the purpose is not fully aligned with the tool's actual interface.

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 explicit guidance on when to use this tool versus alternatives like browser-url-ok, fetch-status, or web-fetch. The existence-checking purpose is implied but not contextualized, and no when-not-to-use information is provided.

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