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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering safety. The description adds valuable behavioral context beyond annotations: it mentions cursor-based pagination and specifies the return content ('full tweet objects with engagement counts'). This goes beyond the bare safety profile, though it doesn't detail rate limits or error conditions.

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 two sentences with no wasted words. The first sentence states the core action and pagination, the second provides usage guidance and return information. The key differentiator (specific community vs. all) is front-loaded.

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 read-only tool with an output schema, the description is nearly complete. It covers the scope (specific community), pagination, and return contents (engagement counts). The only minor gap is that it doesn't explicitly state how to obtain the community_id, but that is likely obvious or covered by sibling tools like get_twitter_community_info. Overall, an agent has enough to invoke it 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 description coverage is 100%, so both parameters are already documented. The description's mention of 'cursor-paginated' reinforces the cursor parameter's purpose but adds no new syntax or format details. It doesn't clarify the community_id beyond what the schema already says. Baseline 3 is appropriate when the schema covers parameters fully.

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 states a specific verb ('Get') and resource ('posts published inside one specific X Community'), and immediately adds 'cursor-paginated' to convey the core behavior. It explicitly differentiates from the sibling tool get_twitter_community_tweets_all by noting the alternative is for searching across all communities when the target is unknown.

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 clear guidance: use this tool to read what a known community is discussing, and explicitly says to use get_twitter_community_tweets_all when the community is not known. This directly addresses when to use this tool vs. the alternative.

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