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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that the title is 'discarded after the call', giving a minor hint about memory behavior. It does not clarify whether the call involves network access, whether it returns a boolean, status code, or error, or any side effects. Critical behavioral details are absent.

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 brief (one sentence), which is efficient, but it omits essential details about how to invoke the tool. Being concise is not valuable when it sacrifices needed instructions. The front-loading is minimal; it states the action but not the input mechanism.

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 parameters, no output schema, and no annotations, this description is severely incomplete. It does not explain how to pass the Wikipedia title, what the expected output is, or any constraints. An agent cannot effectively use this tool without additional information.

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 description adds no meaning to any parameter. Although schema coverage is 100%, the parameter descriptions themselves (e.g., 'Git ref name', 'HTTPS URL to normalize or cite', 'City name for a public weather hint') are entirely unrelated to a Wikipedia title. The description does not specify which parameter represents the title, and none of the schema descriptions mention 'title'. An agent cannot know how to construct a valid call.

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 specific verb and resource: 'Check whether a Wikipedia title exists.' This clearly communicates the core function. However, it does not differentiate from sibling tools like 'browser-url-ok' or 'github-repo-shape', and it fails to connect the stated purpose to any of the nine input parameters, leaving how to supply the title ambiguous.

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. The description does not mention prerequisites, context, or conditions for selection among the sibling tools. An agent has no information to route correctly.

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