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

Beyond the readOnly/openWorld annotations, it discloses two genuinely useful traits: the return is a CSV link rather than inline data, and 'open the link yourself' because the file carries contact details. It also states the auth requirement (Cotlet API key with access). It omits pagination/row-limit or link-expiry behavior, keeping it from a 5.

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?

It is front-loaded with the purpose and keeps sentences short and useful. There is mild redundancy between 'with the same filters as the Clients app' and 'Applies the filters you give, as the Clients app does,' which keeps it just short of a 5.

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?

No output schema exists, and the description compensates by explaining the return is a CSV download link plus how to handle it and what credentials are needed. For a read-only, filter-driven export this is nearly complete, lacking only edge details like result size or link expiry.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning by explaining the intended combination of last_visit_days_ago with has_future_appointment to identify churned clients, and by framing all filters as identical to the Clients app. This is more than the schema conveys.

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 a specific verb and resource ('client list as a CSV download link') and makes the export nature obvious, which cleanly separates it from siblings like mangomint_find_client and mangomint_get_client_timeline. An agent can tell what this does without opening the schema.

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 concrete usage recipe ('Combine last_visit_days_ago and has_future_appointment to find clients who have not come back') and notes the filters mirror the Clients app. However it names no alternative sibling tool or an explicit when-not-to-use condition, so it stops short of full routing guidance.

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