social_get_feed

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

No annotations are available, so the description carries the full behavioral burden. It mentions 'recent' but does not define the time window, sorting, pagination, aggregation behavior, or other important operational details. The description adds minimal behavioral context beyond what the tool name implies.

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, clear sentence with no wasted words. It is extremely concise and front-loaded, earning its place as a quick overview.

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?

With no output schema and no annotations, the description is the only source of contextual information. It fails to explain the return format, the meaning of 'recent', or how the symbol filter interacts with the source selection. For an agent to invoke this tool correctly, more comprehensive information is needed.

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%, with each parameter having a brief description in the schema. The tool description itself does not add any parameter semantics, but the baseline of 3 is appropriate since the schema already documents the parameters.

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 retrieves recent cryptocurrency-related social posts across Twitter, Reddit, and other platforms. It names the resource and provides the action, making the purpose clear. However, it does not explicitly differentiate from similar sibling tools like social_get_trending_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 the many other social tools in the sibling list, such as social_get_trending_posts or social_get_news_sentiment. There are no exclusions or alternative recommendations, leaving the agent to infer usage.

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