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

Annotations already establish this as a safe read (readOnlyHint=true, destructiveHint=false), so the bar is lower. The description goes beyond that by disclosing the visibility scope, the returned fields, the paused-autoflow behavior ('adding a client to a paused Autoflow sends them nothing until it is activated'), and the auth requirement (Cotlet API key with app access).

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 listing purpose is front-loaded and the sentences are compact. The opening fragment 'Everfit: Your Autoflows with name, status...' is slightly awkward, but the rest is efficient and the paused-autoflow note earns its place as operational context.

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 read-only list tool with no output schema and annotations covering safety, the description adequately covers what is returned, whose autoflows are visible, and the auth requirement. Only the exact filtering semantics of 'all' 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?

Schema description coverage is 100% with an enum, so the schema already documents the status filter. The description mentions status but only as 'active or paused', omitting the 'all' enum value present in the schema, so it adds no meaningful parameter detail beyond the baseline.

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 (lists) and resource (Autoflows) with the scope of what is returned: name, status, and client count. It also scopes visibility as 'your own and those shared with the team', which cleanly separates it from the sibling everfit_add_client_to_autoflow.

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?

The listing context is implied (to inspect autoflows), but there is no explicit when-to-use or when-not-to-use guidance, nor a named alternative. Given the only related sibling is a write operation, the intent is inferable but not stated.

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