get_trending_subreddits

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions error handling (Raises section) and the return format (dictionary with basic info), which adds value beyond the input schema. However, it lacks details on rate limits, authentication needs, or what 'trending' means algorithmically, leaving gaps in behavioral understanding.

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 well-structured and front-loaded, starting with a clear purpose statement followed by organized sections for Args, Returns, and Raises. Every sentence adds value without redundancy, making it efficient and easy to parse for an AI agent.

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 tool's low complexity (1 optional parameter) and lack of annotations/output schema, the description is adequate but has clear gaps. It covers the parameter and basic return format but doesn't explain the 'basic info' structure or provide full behavioral context (e.g., what 'trending' entails). This meets minimum viability but could be more complete.

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 description adds significant meaning beyond the input schema, which has 0% coverage. It explains that 'limit' controls the maximum number of trending subreddits returned, specifies the valid range (1-50), and notes it's optional with a default of 5 (implied from schema). This compensates well for the schema's lack of descriptions, though it doesn't detail the structure of the returned basic info.

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's purpose with a specific verb ('Get') and resource ('currently trending subreddits'), making it immediately understandable. It distinguishes itself from siblings like get_subreddit_info or get_top_posts by focusing on trending content rather than specific subreddit details or top posts. However, it doesn't explicitly contrast with all siblings, keeping it at a 4 rather than a 5.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention when to prefer get_trending_subreddits over get_top_posts or search_posts for discovering content, nor does it specify any prerequisites or exclusions. This lack of context leaves the agent without clear usage direction.

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