get_top_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 that it operates on scraped data and returns top posts by score, which is useful behavioral context beyond the annotations. It does not, however, disclose any rate limits or data staleness concerns.

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 two short sentences with no wasted words. However, 'Great for finding popular content' is somewhat generic and could be replaced with more specific guidance. Overall, it is front-loaded with the core action.

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 no output schema and moderate complexity (3 params), the description adequately states what it does and the source of data. It does not describe the return format (e.g., a list of posts with titles, scores, etc.), which leaves some ambiguity about what the agent will receive.

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?

Input schema coverage is 100%, so the baseline is 3. The description does not add any additional meaning to the parameters beyond what the schema provides (target, is_user, limit). The phrase 'by score' hints at ordering but is not parameter-specific.

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 it retrieves top posts by score from a scraped subreddit or user, with a specific verb 'Get' and resource 'top posts'. It implies popularity filtering, differentiating from 'get_posts' which likely returns all posts. However, it doesn't explicitly contrast with siblings like 'search_reddit'.

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 includes 'Great for finding popular content' as a use case, but provides no explicit when-to-use or when-not-to-use guidance. No alternatives are mentioned among the seven sibling tools, leaving the agent to guess when to use this over 'get_posts' or 'scrape_subreddit'.

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