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

With no annotations provided, the description must carry the full behavioral burden. It only states 'Title discarded after the call,' which is an odd note given no parameter is clearly a title, and omits any mention of side effects, authentication, return format, or error behavior. The disclosure is minimal and partially misleading.

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 only two sentences and technically concise, but it is under-specified rather than efficiently structured. It lacks essential information about the primary input and expected usage, so the brevity is a liability, not a strength.

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 optional parameters, no required ones, no output schema, and no annotations, the description is severely incomplete. It does not explain which parameter to supply for the stated check, what the tool returns, or how it relates to the sibling tools, making it impossible for an agent to call correctly.

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?

Schema coverage is 100%, so each parameter has a description, but those descriptions are generic (e.g., 'Git ref name', 'City name for a public weather hint') and do not align with the stated Wikipedia-title purpose. The description adds no meaning beyond the schema and fails to identify which parameter should receive the title, creating a semantic gap.

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 clear verb and resource: 'Check whether a Wikipedia title exists.' However, it does not map this purpose to any of the 9 input parameters, none of which appear to represent a Wikipedia title. The tool name reinforces the purpose, but the schema is unrelated, leaving the agent uncertain how to invoke it.

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 on when to use this tool versus alternatives. Sibling tools like browser-url-ok, domain-shape, and file-path-ok suggest a family of shape-checking tools, but the description offers no context on distinguishing this tool from them or on prerequisites for calling it.

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