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

No annotations are provided, so the description carries the full burden. It mentions 'Title discarded after the call,' implying no persistence, but no parameter is named 'title'—a mismatch. It does not disclose side effects, permissions, return format, or how other parameters are handled. For a tool with zero annotation coverage, this is insufficient.

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 very short (two sentences) but the second sentence about 'Title discarded' is confusing because no parameter is called 'title.' The brevity is not backed by completeness; it under-specifies the tool's actual interface. The structure is not front-loaded with the most critical info, since the parameter-to-title mapping is missing.

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 9 parameters, no required fields, no output schema, and no annotations, the description should explain how to invoke the tool and what it returns. It fails to do so. The agent cannot determine which parameter holds the Wikipedia title, what the tool returns, or any error conditions. This is inadequate for correct usage.

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 description coverage is 100%, so the baseline is 3. The schema descriptions for each parameter (e.g., 'Git ref name; discarded after the shape check') already provide meaning. The tool description adds nothing about parameters, so it neither helps nor hurts beyond 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 clearly states the tool's purpose: 'Check whether a Wikipedia title exists.' This is a specific verb-resource pair that distinguishes it from sibling tools like browser-url-ok (URLs) and file-path-ok (files). However, the description does not indicate which parameter corresponds to the title, leaving a gap in execution.

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?

The description provides no guidance on when to use this tool versus alternatives. It neither names any sibling tool nor gives context for choosing this over others like search-query-len or normalize-url. The agent must infer usage from the name and purpose alone.

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