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

The annotations already declare readOnly=true, destructive=false, idempotent=true, and the description is consistent with them by stating it 'opens nothing by itself.' It adds useful context about the return payload (screens, buttons, fields) and the API-enablement prerequisite, but says nothing about failure modes, rate limits, or what happens if the returned steps cannot be followed in the browser session.

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?

Three tight sentences, front-loaded with the action and its non-obvious caveat, then the follow-up tooling, then the reason the official API is not an option. No filler or redundant restatement of the title.

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, no-output-schema tool the description covers the essentials: what is returned, that nothing is mutated, and which tools complete the job. The only gap is guidance on what to do if the described screens or fields do not match the user's live AroFlo UI.

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 allows no additional properties, so there is nothing extra for the description to explain. Baseline 4 applies; the description correctly avoids inventing parameter details that do not exist.

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 (create a task in the user's own AroFlo account) and immediately qualifies the mechanism: it returns a step-by-step procedure rather than performing the write. This resolves the mismatch between the name 'create_task' and the read-only behavior. It does not explicitly contrast with siblings such as aroflo_list_tasks, but it does route the agent onward to the cotlet_browser_* 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?

Gives a clear two-step workflow: call this to obtain the procedure, then execute it with cotlet_browser_* in the user's AroFlo Cloud Browser. The note that AroFlo's REST API is off by default implicitly answers 'why not use the API instead.' There is no explicit when-not-to-use guidance against the other aroflo_* siblings.

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