get_community

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

No annotations are provided, so the description carries the full burden. It only says 'Get a Twitter Community by ID' and offers no insight into authentication, return behavior, error handling, or whether the community must be public. The read-only nature is implied but not elaborated.

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 extremely concise: two short lines that state the purpose and parameter meaning. No fluff or redundancy. This is an appropriate size for a simple get-by-ID tool.

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 is a simple getter with one parameter and has an output schema, so the description does not need to explain return values. The description sufficiently identifies the tool's function for selection and invocation. However, it lacks any context about edge cases or community visibility, which could matter, but given the simplicity, it is mostly 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 coverage is 0%, so the description must compensate. It says 'community_id: The community ID,' which adds minimal meaning beyond the parameter name itself. It does not clarify expected format, difference between string/integer, or any constraints. The description is essentially redundant with 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?

Description clearly states the tool retrieves a Twitter Community by ID, using the specific verb 'Get' and resource 'Twitter Community by ID.' This distinguishes it from sibling tools like search_community and get_community_members, which have different purposes.

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?

Usage is implied: you use this when you have a community ID and need community details. However, there is no explicit guidance on when to prefer this over search_community or get_community_tweets, nor any mention of alternatives or exclusions. The context is minimal.

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