get_user_tweets

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

Annotations already declare readOnly, idempotent, openWorld, so safety is covered. The description adds the useful fact that results are filtered to exactly one author, but leaves open whether retweets/replies are included and says nothing about pagination caps (page 1-9, limit 1-30) or rate-limit 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?

Two short sentences, front-loaded with the purpose and followed by the implementation relationship. Nothing is wasted or buried.

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 a full parameter schema and an output schema present, the description has little structural burden, but it is silent on retweet/reply inclusion semantics ('exactly that author' is ambiguous) and pagination depth, which are the remaining facts an agent needs to call it correctly.

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 every parameter including freshness, sort, enrich and include_quoted is already documented inline. The description only maps the required username into the from: operator, which is a small addition over the schema — 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?

States a specific verb and resource (fetch recent posts from one X account) and explicitly positions itself relative to search_tweets. It does not distinguish itself from get_tweets, the other obvious sibling for retrieving posts, so an agent must still infer that difference.

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?

Implies the use case — you know the author handle and want only their posts — and names the alternative (search_tweets with from:<username>), making the two interchangeable by construction. No explicit when-not guidance or note about when get_tweets would be preferable.

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