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

The description discloses only 'Billing per call: 1 Credits.' It does not mention side effects, permissions, rate limits, or any other behavioral traits. With no annotations, the description carries full burden but fails to address 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 description is extremely short, but it is not concise in a useful way; it repeats the title and adds billing info. It lacks a structured explanation of the tool's function.

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 the simple tool and single parameter, the description should at least state what the tool returns or when to use it. It does neither, making the description incomplete for understanding the tool's role.

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 lists a single 'subreddit' parameter with an example, but the description does not clarify its meaning. It merely repeats 'Subreddit.' without explaining that it is the subreddit name or how it is used.

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 only repeats the title and adds 'Group: Subreddit.' It does not explicitly state that the tool retrieves the list of moderators for a given subreddit, making the purpose unclear.

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 use this tool versus alternatives like get_subreddit_about or get_subreddit_comments. The description provides no context for selection.

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