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

The only behavioral disclosure is 'Title discarded after the call', which suggests the title is not retained. However, with no annotations provided, the description carries the full burden and also fails to explain network access, authentication, if any side effects occur, or what the return signal means.

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 and front-loaded, with only two sentences and no filler. Its structure is clean but slightly disjointed because the second sentence refers to a 'title' input that is absent from the schema.

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?

For a tool with 9 optional parameters, no output schema, and no annotations, this description is far too thin. It does not tell the agent which parameter should be used, whether multiple parameters are allowed, what the expected response is, or what side effects/constraints apply, so an agent cannot invoke it confidently.

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 even though the tool description adds no parameter-level meaning. The description does not map any schema property to the 'title' it mentions, and the nine optional parameters appear unrelated to checking a Wikipedia 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 specific action: 'Check whether a Wikipedia title exists', which conveys a distinct purpose and is more informative than the sibling tool names. It is not a 5 because it does not explain how this differs from neighboring existence-checking tools or identify which schema property actually supplies the title.

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 about when to use this tool versus other shape/existence tools like browser-url-ok or github-repo-shape, and no mention of required preconditions or alternatives. The phrase only implies a general existence-checking use case without giving the agent decision rules.

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