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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention behavior, return values, side effects, authentication, or rate limits beyond a billing note. The description is devoid of any functional behavior.

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 text is short but not effectively concise—it conveys almost no useful information. The few words used are mostly metadata, not specification, so this is under-specification rather than efficient communication.

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 has no output schema and a single parameter, but the description fails to compensate with any operational details. Given the existence of similar sibling tools and the absence of structured metadata, the description is completely inadequate.

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 description coverage is 0% and the description does not mention the 'subreddit' parameter at all. While the parameter is self-explanatory, the description adds zero value beyond the schema's example field.

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 is essentially a fragment: 'Subreddit Wiki Revisions Group: Subreddit Wiki. Billing per call: 1 Credits.' It restates the tool's name without explaining what the tool does. There is no verb, resource, or scope, and it does not distinguish from siblings like get_subreddit_wiki_page_revisions.

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 given about when to use this tool vs. alternatives. Sibling tools include get_subreddit_wiki_page_revisions and get_subreddit_wiki_page, but the description offers no exclusions or context for selecting this tool.

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