Get Trending Posts

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

The description adds context about compatibly beyond the readOnlyHint annotation, noting that it works only on Mastodon-compatible instances with a trends API. This is useful behavioral disclosure, though it does not cover error handling or rate limits.

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, front-loaded sentence of 15 words that clearly conveys the purpose without redundancy. It achieves conciseness while including essential context.

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 adequate for a simple read tool with an output schema. It provides the domain context and instance compatibility, though it does not address failure cases or usage with non-supporting instances.

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 100% (domain and limit are described). The description adds no parameter-specific detail beyond the overall context, so it meets the baseline without significant added value.

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 action ('get'), the resource ('trending posts'), and the context ('on a fediverse instance'). It also specifies the scope with a parenthetical about Mastodon-compatible instances that expose a trends API, which helps distinguish it from sibling tools like get-public-timeline or fetch-timeline.

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 implies usage for instances with a trends API but does not explicitly state when to use this tool over siblings like get-trending-hashtags or get-public-timeline. No when-not or alternative guidance is provided.

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