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

With no annotations, the description carries the full burden and does well: it discloses that output is HTML (not wikitext), includes the latest revision and text license, that media licenses are separate, that HTML must be sanitized before rendering, and that gateway credentials/charges apply. It stops short of describing pagination or failure behavior, but the behavioral profile is substantially richer than the schema.

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?

Purpose and return shape are front-loaded in the first sentence, with licensing and sanitization guidance following. The gateway billing sentence is slightly peripheral but relevant to authorization. Overall efficient with no significant padding.

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?

No output schema and no annotations, but the description explains the return content (HTML plus latest revision plus text license) and the operational constraints (media licensing, sanitization, gateway auth). For a single-parameter read tool this is essentially sufficient, missing only edge cases like missing-page behavior.

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% and the single 'title' parameter is fully documented in-schema (article title or page key, URL-encoded path segment). The description adds no extra meaning about the parameter, so the schema does all the work and the baseline 3 applies.

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 specific verb and resource: 'Retrieve an English Wikipedia article as HTML with its latest revision and text license.' This is clearer than the tool name 'get_page_title' and distinguishes it from intro-only siblings like wikimedia_get_zh_article_intro. However, it never names a sibling explicitly to contrast against.

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 republishing guidance ('credit Wikipedia contributors, link to the original article') implies the use case is content reuse, but there is no explicit when-to-use or when-not-to-use versus siblings such as wikimedia_get_zh_article_en or wikimedia_get_revisions. Usage is only latent in the operational notes.

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