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

With no annotations, the description carries full burden for behavioral disclosure. It only states 'Title discarded after the call,' but does not explain how the title is supplied, what happens if it doesn't exist, or what the output looks like. No other behavioral traits are disclosed.

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?

While the text is only two sentences, it is under-specified rather than concise. The description fails to convey essential information (how to pass the title), and the statement 'Title discarded after the call' is ambiguous. No useful structure or front-loading of critical info is present.

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 required fields, and no output schema, the description is grossly inadequate. It does not clarify which parameter is relevant, what the tool returns, or any edge cases. An agent cannot reasonably invoke this tool correctly.

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 coverage is 100%, but the description's central concept—'title'—appears nowhere in the schema. The description adds no meaning to any of the 9 parameters and actually conflicts with them. An agent would be at a loss to know which parameter corresponds to the 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 clear verb+resource ('check whether a Wikipedia title exists'), but the schema provides no parameter for a title. This makes the purpose misleading—an agent cannot map the described behavior to any of the 9 schema fields. It is not a tautology, but it is confusing due to the mismatch.

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 versus siblings like 'browser-url-ok' or 'fetch-status'. It does not mention any conditions, prerequisites, or alternatives, leaving the agent without direction on selection.

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