Get detailed Reddit posts

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds context about the returned metadata but does not disclose additional behavioral traits such as rate limits, pagination, or authentication requirements beyond what annotations provide.

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 concise at one sentence, front-loading the key purpose ('Recent Reddit posts') immediately. Every word adds value, with no fluff or redundancy.

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 an output schema and clear annotations, the description covers the essential purpose. However, it omits any mention of authentication prerequisites, pagination behavior, or the meaning of 'detailed'—though the output schema likely compensates for return value details.

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 description coverage is 50% (limit parameter lacks description). The tool description does not compensate by explaining the limit parameter or its effect; it only mentions 'recent' posts, which does not clarify the integer range or default. The profile parameter is described but the limit remains opaque.

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 'Recent Reddit posts published from a profile' with 'platform-side metadata (subreddit, flair, score, …)'. It uses a specific verb ('get') and resource ('Reddit posts'), and distinguishes itself from sibling tools by focusing on detailed Reddit posts with metadata.

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 guidance on when to use this tool versus alternatives is provided. The description lacks 'when-to-use' or 'when-not-to-use' instructions, and does not reference any sibling tools for comparison, leaving the agent without context for selection among many similar 'get_*' tools.

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