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

With no annotations provided, the description carries the full burden and discloses meaningful behavior: flat 1-credit pricing, no charge for empty results or failures, and a cache=true option that produces free 24h-cache hits with an always-fresh default. This goes well beyond a typical one-liner by explaining the cost model and failure-charging policy. It omits auth and rate limits, but those are minor for a read-style card endpoint.

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 payload list is front-loaded and each clause is short, but 'Flat 1 credit. Costs 1 credit.' is a redundant pair that wastes an entire sentence. Beyond that duplication, every other part earns its place and the structure is scannable.

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 2-parameter tool with no output schema and no annotations, the description covers the returned fields, the pricing and no-charge-on-failure policy, and the caching escape hatch — leaving little an agent must guess. The schema fills in all parameter semantics, and missing items like auth or rate limits are secondary for a low-complexity read endpoint.

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%, so the schema already documents accepted url formats and the cache boolean with solid examples. The description adds value beyond the schema by linking cache=true to a 0-credit outcome and stating the default always-fresh behavior, which directly affects how an agent should set the parameter. This complements rather than repeats the schema.

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 names the resource (subreddit) and the exact payload (id t5_…, members, activeUsers, rules[], ISO createdAt, nsfw/type), framing the operation as a 'card' retrieval. This clearly differentiates it from siblings like reddit_subreddit_posts and reddit_subreddit_search, which fetch posts or search results rather than profile metadata. The lack of an explicit verb is mitigated by 'card' plus the concrete field list.

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 field list implies this tool is for subreddit metadata rather than posts or transcripts, but no sibling is named and no explicit when-to-use or when-not-to-use condition is stated. The schema's url parameter adds a cross-platform exclusion, yet the description itself offers no routing guidance among the several reddit_* siblings. Usage context is implied rather than stated.

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