favorite_tweet

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

Annotations reveal readOnlyHint=false (write operation) and openWorldHint=true (side effects possible). The description does not add beyond stating the obvious API usage; no mention of idempotency, rate limits, or effects on already-liked tweets.

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?

One short sentence, no extraneous words, front-loaded with key information.

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 simple write operation with one parameter and no output schema, the description lacks completeness. Missing: success indication, error conditions, idempotency, and any side effects.

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 has 1 required string parameter (tweet_id) with 0% schema description coverage. Description implies tweet_id identifies the tweet to like but provides no format, validation, or additional context beyond 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?

The description clearly states the action ("Like (favorite)") and resource ("a tweet"), matching the tool name. It is distinct from sibling tools like bookmark_tweet, retweet_tweet, etc.

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 on when to use this tool vs alternatives, no prerequisites, conditions, or error states. The description is purely declarative without usage context.

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