Discover Social Posts

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

Annotations already mark this as read-only, idempotent, and non-destructive, so the description adds non-overlapping context: it costs 2 orchyn credits, supports pagination via offset, and returns inline thumbnails intended to render in chat. These are behavioral details not present in annotations.

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 dense yet efficient: every sentence contributes something — scope, result contents, chat behavior, pagination, batch analysis, sibling differentiation, and cost. It is front-loaded with the core purpose before diving into secondary details.

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 rich annotations and output schema, the description fills all remaining practical gaps: when to choose an alternative, credit cost, pagination command, and chat-oriented output behavior. An agent has everything needed to select and invoke this tool correctly.

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%, so the baseline is 3, but the description adds practical meaning beyond the schema by linking offset to the 'next' command, giving concrete niche examples, and explaining how the returned posts are meant to be used. This helps an agent reason about limit, platform, and pagination choices.

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 opens with a specific verb-resource pair: discovering recent posts for a niche across named platforms and content types. It explicitly contrasts itself with niche_report, so an agent can immediately tell what this tool returns versus what it does not.

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?

It explicitly states when to use this tool (find individual posts to look at) and when to prefer niche_report (pattern across posts). It also documents interaction patterns like saying 'next' for pagination and 'analyze the 2nd one' / 'analyze all' for batch analysis, making usage unambiguous.

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