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

With no annotations, the description carries the behavioral burden and does disclose meaningful traits: flat 2 credits, empty results/failures not charged, and cache=true producing a free 24-hour hit with always-fresh default. It also references the 6-metric tweet return shape. It does not cover pagination, rate limits, or authentication, but enough operational behavior is surfaced for a read-only fetch tool.

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 short and front-loads the purpose, but the cost statement is duplicated ('Flat 2 credits. Costs 2 credits.'), adding unnecessary words. Overall it is compact and scannable.

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 tool has no output schema and no annotations, so the return-value description must carry more weight; 'same 6-metric tweet shape as search' is ambiguous because no equivalent 'search' tool exists among the siblings. Costs, caching, and parameters are well-covered, but the missing explicit output contract leaves a notable gap.

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?

Input schema already describes all 3 parameters at 100% coverage, including URL platform restrictions, cache semantics, and limit range. The prose description mostly repeats these details (e.g., 'free 24h cache hit') rather than adding new parameter-level meaning, so it meets the baseline but adds little extra.

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 'Posts in an X Community', clearly identifying the resource (community posts) and implying a retrieval action. It distinguishes from sibling tools like twitter_community and twitter_user_tweets through the 'community' scope, though it never names an alternative, so it stops short of explicit differentiation.

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?

There is no explicit when-to-use or when-not-to-use statement, nor any named alternative tool. The intended context is implied by 'Posts in an X Community' and the cache/cost notes, but an agent is not told to prefer this over twitter_community or twitter_user_tweets for specific needs.

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