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

With no annotations present, the description carries the full burden. It discloses one behavioral trait: 'Title discarded after the call,' implying the tool is stateless and does not retain input. It does not disclose whether the tool makes a network request, how it handles nonexistent titles, or what it returns, so transparency remains partial.

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 short and front-loads the main purpose in its first sentence. The second sentence adds a statelessness hint, though it is vague and partly duplicates the schema's repeated 'discarded' notes. Overall, it is economical without being wordy.

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 seven input parameters, no output schema, and no annotations, the description is far too thin to support correct invocation. It omits which property receives the Wikipedia title, what the return value means, and how the tool behaves in edge cases such as invalid titles or redirects.

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 documents seven string parameters, but none of them is a Wikipedia title, and the description never maps 'title' to any parameter. The schema fields are refs, URLs, cities, feeds, hosts, JSON, and paths, which creates a direct usability mismatch: an agent cannot determine what value to pass. This is actively confusing rather than merely lacking detail.

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 gives a specific verb and resource: 'Check whether a Wikipedia title exists.' This is clear and distinguishes the tool from most sibling validators by naming Wikipedia titles as the domain. However, it does not explain the relationship between this purpose and the unrelated-looking input parameters.

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 explicit guidance about when to use this tool instead of sibling tools such as normalize-url, validate-json, or file-path-ok. The intended use case is only weakly implied by the one-line description, and no exclusions, prerequisites, or alternative conditions are provided.

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