Get subreddit rules

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

No annotations are present, so the description should fully disclose behavioral traits. It only states it fetches rules and flags risks, but omits details about output format, authentication needs, rate limits, or side effects. The risk-flagging behavior is vague.

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 a single concise sentence that front-loads the main action. It could be slightly more structured by separating the two actions, but it is efficient with no unnecessary words.

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?

For a simple, read-only tool with one parameter and no output schema, the description is minimally adequate. However, it lacks details on output format, error behavior, and the nature of risk flags, which are gaps for an AI agent.

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% for the single parameter 'subreddit', and its description is already explicit. The tool's description adds no new information about this parameter, so the baseline score of 3 is appropriate.

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 clearly states the tool fetches subreddit rules and flags promotional-posting risks, using a specific verb+resource. It also distinguishes itself from sibling tools like preview_text_post and submit_text_post, which deal with posting, not rules.

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 explicit when-to-use or when-not-to-use guidance is provided. The usage is only implied by the purpose, and no alternatives are mentioned despite the presence of sibling tools like health that might offer related information.

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