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

With no annotations, the description must disclose behavioral traits. It only mentions that the title is discarded after the call, which is trivial. It does not state whether network access is involved, error behavior, read-only nature, or any side effects – leaving the agent with no expectations beyond the bare purpose.

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, but it is far too sparse to be helpful. It omits essential details like parameter mapping and output expectations, so it is under-specified rather than appropriately sized.

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 parameters, no output schema, and no annotations, the description is grossly incomplete. It fails to explain how the parameters relate to the task, which parameter holds the title, what the return value indicates, or any operational details. An agent cannot call this tool correctly based on the provided 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?

Although schema description coverage is 100%, the parameter descriptions are generic (e.g., 'Git ref name', 'Public hostname') and have no apparent connection to checking a Wikipedia title. The tool description adds zero parameter meaning and fails to indicate which parameter carries the title, making the tool effectively unusable from the schema alone.

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 purpose: checking whether a Wikipedia title exists. However, it does not differentiate from sibling tools and, critically, does not connect the purpose to any of the 9 input parameters – none of which is a title. This creates ambiguity about how to invoke the tool.

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 on when to use this tool versus alternatives like 'browser-url-ok' or 'normalize-url'. No context about prerequisites, exclusions, or selection criteria is provided.

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