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

With no annotations, the description should disclose behavioral traits (e.g., read-only, pagination, auth needs). It only notes billing and a vague group, omitting any indication of side effects, auth requirements, or response handling. The tool likely fetches data but this is never stated.

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 brief, almost a fragment. While it is short, it is under-specified rather than concise; it lacks essential structure and substance, failing to earn 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?

The tool has 5 parameters, no output schema, and no annotations. The description provides no information about return values, pagination, or how parameters interact. It is completely inadequate for an agent to correctly invoke this tool.

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 only 20% (only auth_token has a description). The description adds zero parameter information, leaving cursor, tweetId, proxyUrl, and resFormat entirely unexplained. This is a major gap.

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 says 'Favoriters by V2 Group: Tweets' which essentially restates the tool name and adds a vague group label. It does not state a specific action or resource (e.g., 'Get users who favorited a tweet'), making it ambiguous and lacking differentiation from siblings like favoritesList or likeV2.

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?

No guidance is provided on when to use this tool versus alternatives, nor any mention of prerequisites or contexts. The description only mentions billing and group, offering no decision support.

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