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

No annotations are present, so the description carries the full burden. It discloses that the title is 'discarded after the call,' which hints at privacy/statelessness, but it does not explain return values, error behavior, network dependencies, or side effects. This is insufficient for a tool with zero annotation coverage.

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 sentence and economical, but its brevity removes critical information needed for correct invocation. The sentence is clear about the action but omits input binding and behavior details, so the conciseness does not serve the agent well.

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 8 parameters, no annotations, and no output schema, a one-sentence description is grossly incomplete. The agent cannot determine what to pass, what the tool returns, or how to interpret the parameter descriptions. This is far below the minimum viable completeness.

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 lists 8 parameters, none of which is named 'title,' and the description does not connect 'title' to any of them. The parameter descriptions themselves (Git ref, city, JSON, etc.) are unrelated to the stated purpose, leaving the agent unable to determine which input to provide. The description adds no meaningful parameter guidance.

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 clearly identifies the tool's resource and purpose, and distinguishes it from siblings like browser-url-ok or file-path-ok. However, the mention 'Title discarded after the call' introduces ambiguity about what the title is or how it is passed, slightly reducing clarity.

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 gives no guidance on when to use this tool instead of other validation tools (e.g., browser-url-ok, file-path-ok). There is no mention of use cases, constraints, or alternatives, so an agent cannot determine the tool's appropriate context.

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