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

Annotations already mark this tool read-only and open-world, and the description's 'Fetch' is consistent. It adds only the 'live' nature and the /communities equivalence; it doesn't disclose pagination, ordering, rate limits, or auth expectations beyond what the schema already documents. No contradiction with 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?

A single front-loaded sentence with no filler; every clause earned its place. The '/communities' reference is useful context, not repetition.

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 simple read-only feed with strong annotations this is nearly sufficient, but no output schema exists and the description doesn't state what fields the posts contain, ordering, or how to source communityId. It remains adequate but not fully complete.

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 only 33% (only authCode is described), and the description does not compensate: communityId is merely called optional and limit is never mentioned. The long authCode explanation lives in the schema, not the tool description, so parameter semantics remain under-specified.

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?

States a specific verb ('Fetch') and resource ('live community_posts feed') and notes the optional filter (communityId). The closing '/communities' equivalence makes the endpoint unambiguous and separates it from sibling community-listing tools.

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 gives no when-to-use guidance or alternative routing. It neither names a sibling (e.g., orbitx__orbitx_social_communities) nor states when to pass communityId versus omit it; 'Same posts as /communities' is an equivalence, not a usage rule.

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