get_trending_posts

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

With no annotations provided, the description carries full burden. 'Get' implies a read-only operation, but the description does not disclose any behavioral traits such as whether it returns paginated results, how trending is determined, or any rate limits. The description adds minimal behavioral context beyond what the tool name already suggests.

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 a single short sentence with no filler words, making it efficient. However, it lacks any structured guidance or examples, but it still earns points for being appropriately sized and front-loaded with the core purpose.

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?

The description is too thin given the tool has 3 parameters and no output schema. It does not explain default behavior when no parameters are provided, what the response format looks like, or how category/timeframe filtering works. The agent would need to make assumptions or call the tool to understand its behavior.

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%, with each parameter having a description. The tool description adds little beyond the schema, only referencing 'various categories' which weakly relates to the category parameter. Baseline 3 is appropriate as the schema carries the semantic weight.

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 verb (Get) and resource (trending/popular posts) with a scope mention of 'various categories'. It is not a tautology, as it adds 'popular' and 'categories' beyond the tool name, but it does not explicitly differentiate from sibling tools like search_posts.

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 does not mention exclusions, prerequisites, or context such as 'use search_posts for specific queries'. The intended use is implied but not explicitly stated.

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