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

No annotations are present, and the description offers no behavioral details such as whether the tool reads data, what output to expect, rate limits, or any side effects. The single word 'Twitter' discloses nothing beyond the platform name.

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 (one word), which is not appropriate given the lack of information. It is under-specified rather than effectively concise, failing to convey any useful meaning.

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 no annotations, no output schema, and only one parameter, the description should explain what data is returned for a given Twitter handle. The word 'Twitter' provides almost no context, making the tool effectively unusable for an agent.

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?

The input schema covers 100% of the parameter (handle) with a brief description 'Twitter handle'. Since schema coverage is high, the baseline is 3, but the description itself adds no extra semantic value beyond the schema's minimal field explanation.

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 is simply 'Twitter', which restates the tool's name without providing any action or resource. It fails to specify what the tool does (e.g., scrape, fetch, or retrieve Twitter data). No verb or object is given, making it a tautology.

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. The sibling list contains numerous platform-specific tools, but the description gives no context for selecting this one instead of others.

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