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

The annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description reinforces this with 'opens nothing by itself', which is consistent. It adds genuinely useful context beyond the annotations: the return shape is procedural instructions, not data, and the follow-up requires browser tools. The API note (REST API exists but is off by default and must be enabled via AroFlo support) explains why a browser path is needed, though it is background rather than behavior of this call.

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 operative information is front-loaded in the first two sentences, which is good, but the second sentence is a dense run-on mixing the return value, the 'opens nothing' guarantee and the next-step tooling. The closing sentence about AroFlo's REST API, including a check date, is tangential to invoking this tool and could be dropped without loss.

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 no parameters, no output schema and full annotation coverage, the description carries the remaining burden and does so: it says what comes back (step-by-step instructions) and what the agent must do next (cotlet_browser_*). It is slightly incomplete in not indicating how large or structured the returned guide is, but for a zero-argument guide tool this is close to sufficient.

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 and the schema is an empty closed object, so there is nothing for the description to disambiguate. Baseline 4 applies. No parameter meaning is missing or misrepresented.

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 states the resource (tasks in the user's AroFlo account) and then explicitly discloses the real output: a step-by-step guide covering screens, buttons and fields rather than the task data itself. That correction is valuable because the name 'list tasks' would otherwise lead an agent to expect records. It loses a point because the opening sentence still frames the tool as listing tasks, so the true purpose only becomes clear in the second sentence.

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 clearly routes the agent: this tool produces instructions, and the actual listing is done with the cotlet_browser_* tools in the AroFlo Cloud Browser. That is an explicit handoff to the alternative tools. It stops short of a 5 because it never states when this tool should not be used (e.g., if a direct read path exists) and gives no ordering or prerequisite steps for the handoff.

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