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

The phrase 'Title discarded after the call' hints that the tool does not persist state, but there is no explicit statement about side effects, permissions, or mutability. With no annotations available, this minimal hint is insufficient.

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 easy to read, which is positive. However, the extreme brevity omits essential information about which parameter is the title and how the check behaves.

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?

The tool lacks any explanation of return values, expected input format, or relationship to the nine schema properties. The mismatch between the stated purpose and the parameter descriptions makes the tool impossible to invoke correctly with confidence.

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 every parameter has a description, those descriptions are unrelated to checking Wikipedia titles (e.g., 'Git ref name', 'City name for a public weather hint'). The descriptions do not clarify how any parameter relates to the tool's stated 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 states a clear action and resource: 'Check whether a Wikipedia title exists.' However, it does not identify which input parameter holds the title, leaving the core purpose ambiguously mapped to the schema.

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 provided about when to use this tool versus the many sibling tools, such as search-query-len or normalize-url. There is no explanation of expected inputs or when it should be preferred.

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