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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false; the description reinforces this with 'opens nothing by itself', which removes the risk of an agent assuming the task is actually created. It also discloses the API plan restriction and the fact that the official MCP server cannot act on the account, useful context beyond structured fields. Missing: any statement about what happens if the plan or UI differs, or failure modes in the returned steps.

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 critical 'opens nothing by itself, use cotlet_browser_*' clause is front-loaded and well placed, but the opening 'from ChatGPT, Claude or any AI agent' is filler, and the final sentence about the official API/plan tiers is supporting justification rather than instruction. The middle sentence is dense but earns its place.

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?

There is no output schema, so the description must describe the return value; it does so explicitly ('returns how to do it step by step (screens, buttons, fields)'). Combined with the no-side-effect guarantee and the handoff to browser tools, an agent has enough to call it correctly. Only the shape/format of the returned steps is left vague.

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 closed (additionalProperties=false), so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter semantics are needed or missing.

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 and outcome (creating a task in the user's Connecteam account) and clarifies the actual deliverable: step-by-step screen/button/field instructions rather than the action itself. The name 'connecteam_create_task' slightly oversells what happens, but the second clause corrects that. It is distinguishable from the mutation siblings such as connecteam_send_message because it points to the cotlet_browser_* tools as the executor.

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 a clear execution path: call this to get instructions, then perform the work with the cotlet_browser_* tools in the Cloud Browser. It also explains why the official API route is unavailable (Expert plan or higher, official MCP only looks up endpoints), which justifies choosing this tool. It stops short of naming when-not-to-use conditions or explicit alternatives among the Connecteam siblings.

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