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

No annotations are present, so the description carries the full burden. It discloses meaningful operational behavior: 'Costs 1 credit', 'Empty results and failures are never charged', and the cache freshness policy with default always-fresh. This goes beyond the basic read-only nature implied by 'metadata' and helps the agent anticipate costs and side effects.

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 compact and front-loaded: resource, returned fields, cost, failure policy, and cache option. Each sentence carries distinct information with no filler.

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 two-parameter metadata endpoint with no output schema, the description covers the return shape via field enumeration and clarifies cost, failure, and cache behavior. It does not describe error responses or rate limits, but for this simple read endpoint the essential calling context is present.

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 100%, so the baseline is 3. The description restates cache behavior ('Pass cache=true for a free 24h cache hit') but the schema already documents '0 credits on hit' and the default false; no new parameter meaning is added. The url parameter is already richly described in 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 opens with 'X Community metadata' and enumerates the returned fields (ISO createdAt, flat creator handle, isNsfw + bannerImage, rules[]), making the resource and scope clear. It lacks an explicit verb like 'fetch' and doesn't name a sibling, but the metadata focus distinguishes it from twitter_community_tweets.

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 and schema give clear input constraints: only community URLs/IDs, not tweet/status URLs, and the platform must match. It also provides cache guidance ('Pass cache=true for a free 24h cache hit'). However, it does not contrast this tool with siblings such as twitter_community_tweets or twitter_profile, leaving when-to-use vs alternatives implied.

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