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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new context: ordering (newest first), absence of any sentiment or analysis field, and a prompt-injection warning about untrusted third-party content. What is missing is any note on empty results or tweet retention/refresh behavior.

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 first two sentences are tight and front-loaded, but the 'Data sources' paragraph is about actor records, not tweets, and consumes over half the text with off-topic provenance caveats. That material belongs on list_actors, not here, and dilutes the signal.

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?

An output schema exists, so return-shape explanation isn't needed, and pagination is covered by the cursor parameter. However, for a simple read tool the description spends its length on irrelevant actor sourcing while leaving tweet-specific behavior (volume, currency, whether retweets are included) unstated.

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 id, limit (1-500), and cursor are already fully documented. The description reinforces 'newest first' but adds no syntax or semantics beyond what the schema states — the baseline 3 applies.

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 opening sentence gives a specific verb+resource ('paginated tweets linked to this actor, newest first') and the second names the payload shape (raw text plus engagement counts). No sibling tool lists tweets, so no confusion arises, though the purpose statement is then buried under unrelated actor-record material.

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 implies when to use it (raw signal retrieval instead of analysis) and the third-party-content caveat sets reporting expectations, but there is no explicit statement of when to prefer this over, say, list_transcripts or search, nor any prerequisites beyond the id resolution already in the schema.

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