subreddit_rules

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

With no annotations, the description carries full burden. It clearly states it reads and flags rules mentioning self-promotion, which implies a safe, read-only operation. It doesn't disclose output format or permissions, but for a read tool, this is adequate and not misleading.

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 concise sentences with no waste. The primary action is front-loaded, and the usage instruction is a single clear directive. Perfectly sized.

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 simplicity (one parameter, read-only, no output schema), the description covers the essential behavior and usage. It doesn't explain return format, but since there is no output schema, that's not a required addition. The instruction to call before posting is valuable contextual guidance.

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 only parameter, 'subreddit', has a type and title but no description. Schema description coverage is 0%, and the description doesn't clarify the expected format (e.g., with or without 'r/'). The description adds no extra meaning beyond the schema, leaving the agent to infer the value.

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 uses a specific verb 'Read' and names the resource ('a subreddit's rules, size and description') and the specific action of flagging self-promotion mentions. It clearly distinguishes from the sibling tools post_status and threadfox_full_kit, which sound unrelated.

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?

The description explicitly instructs when to use it: 'Call this before writing any post for that community.' This provides clear usage context, though it doesn't mention alternatives or exclusions. Since there are siblings, it doesn't explicitly route away from them, but the usage timing is clear.

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