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

No annotations are provided, so the description carries the full burden for behavioral transparency. The only potentially useful behavioral detail is 'Billing per call: 1 Credits,' but the description never says whether this is read-only, what the returned page format is, or how errors for missing pages are handled.

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-loaded, but its content is mostly categorical/billing metadata rather than a substantive functional specification. Brevity here is not valuable because the text does not explain what the tool does.

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?

This is a very small tool surface, but it is still incomplete: nothing states that it returns a wiki page, what page parameter format is expected, or how this differs from related wiki tools. Without an output schema or annotations, the description needed to provide at least basic return/usage context and it does not.

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 description adds no information at all about the parameters. With 0% schema description coverage, the tool description should have explained that 'page' is a wiki page slug and 'subreddit' indicates the target community; instead, only names and examples in the schema do any work.

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 grouping label and billing note: 'Subreddit Wiki Page Group: Subreddit Wiki. Billing per call: 1 Credits.' It does not state an action, such as retrieving or fetching a wiki page, nor does it explain what the response will contain. It mostly restates the title/name without giving a usable purpose.

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 this tool should be used or when it should not be used. This is especially harmful because many sibling tools exist for wiki pages, wiki indexes, wiki revisions, and other subreddit content, and the description provides no way to distinguish this tool from them.

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