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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, and the description reinforces this with 'opens nothing by itself', which is genuinely useful for an agent deciding whether it is safe to call. It also discloses the return shape (step-by-step screens, buttons, fields) and the reason browser automation is needed (no public pro API). It omits any prerequisite or failure condition, such as what happens if the user is not logged into Angi.

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 key constraint ('opens nothing by itself') is front-loaded in the second clause and the follow-up instruction comes immediately after, so an agent gets the essential routing information in the first two sentences. The closing note about Angi's API is a dangling fragment ('Angi's official API: Angi has no public API for pros') and the dated check adds context but is worded awkwardly.

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 zero-parameter, annotation-covered, no-output-schema guide tool, the description covers purpose, non-execution semantics, return content, and the required follow-up toolset. Only environment prerequisites (Angi login state, Cloud Browser session validity) are left unaddressed.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. No misleading parameter hints are given.

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 makes the crucial distinction that this tool does not perform the action but returns step-by-step instructions (screens, buttons, fields) for requesting a homeowner review in the user's own Angi account. That verb-plus-resource framing is clear and separates it from action-performing siblings like angi_reply_to_review. It stops short of explicitly contrasting itself with the other angi_* listing/messaging tools.

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 gives an explicit workflow: call this to get the steps, then carry them out with the cotlet_browser_* tools in the user's Angi Cloud Browser, and it names the purpose-built guide sibling family rather than leaving the follow-up path implicit. There is no stated when-not-to-use case (e.g., when the review was already requested), so it falls short of a full routing rule.

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