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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only states that the title is discarded after the call, which hints at statelessness, but does not mention whether network access occurs, whether any side effects exist, what happens on failure, or if any authentication is needed. This is insufficient for a tool that likely performs an external lookup.

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 extremely concise at one sentence, which is positive for brevity, but it omits essential information such as how to supply the title and what the expected behavior is. It is under-specified rather than appropriately concise, so it does not earn a higher score.

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 the tool has 9 optional parameters, no output schema, and no annotations, the description is woefully incomplete. An agent has no idea which parameter to populate to check a Wikipedia title, nor what the tool returns or what side effects to expect. This is a critical gap for a tool that appears to be a specialized checker among many similar ones.

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?

While schema coverage is 100% (each parameter has a description), those descriptions are generic and unrelated to the tool's purpose (e.g., 'Git ref name; discarded after the shape check', 'City name for a public weather hint'). The tool description does not clarify which parameter holds the Wikipedia title, and none of the parameter names suggest it. The description adds no semantic value beyond the schema, and the schema itself is misleading relative to the stated function.

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.' This is unambiguous about the core action. However, it does not distinguish from sibling tools like 'browser-url-ok' or 'search-query-len' that might also involve URL or text validation, so it lacks explicit differentiation.

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 tools (e.g., 'normalize-url', 'validate-json', 'file-path-ok'). The description does not mention prerequisites, alternatives, or conditions that would lead an agent to select this tool over others.

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