like_tweet

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

No annotations are provided, so the description carries the full burden. It discloses the implicit state dependency (must be on the tweet page) which is valuable. However, it doesn't cover idempotency, what happens if the tweet is already liked, or the return value. For a mutation tool with zero annotations, this is a reasonable but not thorough disclosure.

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 sentences, front-loaded with the action, immediately followed by the operational dependency. Zero waste.

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?

Given the tool's simplicity (zero params, no output schema), the description covers the essential context: the action and the required page state. It lacks only edge-case behavior for a mutation, but the core guidance is complete.

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?

Zero parameters, so the baseline is 4. The description correctly implies the tool needs no parameters because it relies on browser context.

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 ('Like') and resource ('the tweet'), and adds the crucial constraint that it operates on the currently open tweet page. This distinguishes it from sibling actions like retweet and quote_tweet which target a specific tweet by ID.

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?

Explicitly tells the agent to call navigate_to_tweet first, naming the exact prerequisite sibling. This is a textbook when-to-use instruction that prevents a failed call on the wrong page.

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