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

No annotations are present, so the description must disclose behavior. It only notes 'Title discarded after the call,' which is unhelpful, and it fails to mention the return type, side effects, or error conditions. This is insufficient for a tool with nine optional parameters.

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 concise sentence, but it is under-specified and lacks essential details. It is not appropriately sized for a tool with nine parameters and no other documentation.

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 nine optional parameters and no output schema, the description is grossly incomplete. It does not explain what the tool returns, how to select the title parameter, or any constraints on inputs, making correct invocation impossible.

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 has 100% coverage, so each parameter has a description, but the tool description does not explain how any parameter relates to the Wikipedia title check. The schema descriptions (e.g., 'Git ref name', 'City name for a public weather hint') appear unrelated, and the description does not clarify which parameter is 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 clear verb and resource ('Check whether a Wikipedia title exists'), but it does not identify which of the nine input parameters provides the title, making the purpose ambiguous. It also does not distinguish this tool from siblings like browser-url-ok or file-path-ok.

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 on when to use this tool versus alternatives. No prerequisites, exclusions, or comparisons are provided, leaving the agent without any selection criteria.

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