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

With no annotations at all, the description carries the full burden, and it does add real value by disclosing that the call uses the caller's OpenAny gateway credentials and that charges and authorization are decided by the gateway. However it says nothing about ordering (latest-first?), the 20-result cap behavior, or whether further revisions are reachable, which are key behavioral facts for a 'recent revisions' call.

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?

Two sentences, front-loaded with what the tool returns, followed by a short billing/auth note that is relevant to an agent deciding whether to call it. No redundant restatement of the schema enums.

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 exists, and the description compensates reasonably by enumerating the returned fields. But for a seven-parameter, seven-of-seven-required historical query, the absence of ordering/limit behavior leaves gaps an agent would want closed before calling.

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 five of seven parameters are fixed enums, so the schema does most of the work; the description adds only that 'titles' means an English Wikipedia article title. It does not clarify the rvlimit cap or the timestamp/comment semantics beyond echoing the returned fields.

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?

States a specific verb and resource ('List recent revisions of an English Wikipedia article') and names the returned fields (revision IDs, UTC timestamps, edit summaries), so the operation is unambiguous. It does not explicitly distinguish itself from nearby siblings such as wikimedia_get_revision_from_compare_to or wikimedia_get_page_title, which keeps it from a 5.

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 pick this tool over the sibling revision/history tools (e.g., wikimedia_get_revision_from_compare_to, wikimedia_get_page_title), and no stated prerequisites such as needing the exact article title. Usage is only implied by the verb 'List ... revisions'.

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