social_get_twitter_stats

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

With no annotations provided, the description carries the full burden. It indicates a read-only 'Get' operation and enumerates the output metrics (followers, tweets, engagement), but it does not disclose potential limitations, data freshness, or rate limits. For a simple getter, this is minimally sufficient and does not contradict any 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 a single, front-loaded sentence that efficiently states the action and resource, lists the key metrics, and contains no filler or redundant information.

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?

For a tool with one parameter and no output schema, the description adequately conveys the input and expected output metrics. It does not cover edge cases or data source details, but it is complete enough for an agent to select and invoke the tool correctly, especially given the simple nature of the operation.

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 input schema already documents the single parameter `symbol` with a clear description ('Coin symbol (e.g., 'BTC')') at 100% coverage. The tool description only says 'for a cryptocurrency,' which adds no new meaning or constraints beyond the schema.

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') and the resource ('Twitter/X statistics for a cryptocurrency'), with a parenthetical specifying the exact metrics (followers, tweets, engagement). This differentiates it from similar siblings like social_get_reddit_stats and social_get_github_stats.

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 the tool should be used when Twitter/X stats are needed, but it gives no explicit guidance on when to choose this over alternatives or when not to use it. No alternative tools are mentioned, though the sibling context suggests such differentiation would be helpful.

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