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

With no annotations, the description carries the full burden of behavioral disclosure. It only states that the title is discarded after the call, which is a data-handling note, but it does not explain network access, rate limits, or side effects. The tool's actual behavior (e.g., how it checks Wikipedia) is opaque. The statement also seems inconsistent with the schema, as no 'title' parameter exists.

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, which is concise and front-loaded with the main action. However, it is too terse to convey the complexity of a tool with 9 optional parameters and no required ones. The sentence is not misleading but under-specifies the tool's scope, so it earns a middling 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 high complexity (9 parameters, none required, no output schema), the description is grossly incomplete. It does not explain the role of each parameter, how the tool determines if a title exists, or what the output looks like. An agent cannot confidently invoke this tool based on the description alone. The description is inadequate for the tool's complexity.

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 description coverage is 100%, so each parameter has a description. The tool description adds no additional meaning about the parameters—it does not indicate which parameters are relevant to the title check or how they map to the functionality. Baseline 3 applies because the schema does the heavy lifting, but the description fails to clarify the relationship between parameters and purpose.

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 a specific verb and resource: 'Check whether a Wikipedia title exists.' It names the action and the object. However, it does not differentiate from sibling tools like 'browser-url-ok' or 'domain-shape' explicitly, and the mention of 'title' conflicts with the schema that has no 'title' parameter, which may confuse agents. The purpose is clear but not fully disambiguated.

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. There are no context cues, exclusions, or references to sibling tools. An agent has no basis to choose this over a more specific tool like 'fetch-status' or 'normalize-url'.

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