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

Annotations already cover readOnly, idempotent, openWorld, and non-destructive traits. The description adds context beyond those annotations by specifying that the result is returned under `community_info` and by framing the operation as qualifying a community before further retrieval.

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?

Three sentences, all informative, with the core purpose and expected return value front-loaded and no filler. The alternative-usage sentence is efficient and earns its place.

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 only one parameter, complete annotations, a likely output schema, and a sibling routing instruction, the description covers every decision an agent needs to invoke this tool correctly. Nothing important appears missing.

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 the baseline is 3. The description adds value by clarifying the ID's format ('numeric community ID') and its role within X Community context, which is not made explicit in the schema's generic 'ID of the community'.

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 uses a specific verb ('Get metadata') and identifies the exact resource ('an X Community by its numeric community ID') plus the fields returned (name, description, member count, access rules). It clearly distinguishes itself from sibling tools like get_twitter_community_members and get_twitter_community_tweets_all.

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?

It explicitly states when to use the tool: 'Use this to qualify a community before pulling its members or posts.' It also names an alternative for discovering communities by topic: search their posts with get_twitter_community_tweets_all.

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