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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real value beyond that: it discloses the sort order ('newest first') and the auth prerequisite ('Needs the user's Cotlet API key with access to this app'), which the annotations do not provide.

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?

Front-loaded and reasonably short, but the entry list is stated twice ('past and upcoming appointments, sales, timeline notes and form submissions' then again as 'appointments, sales, timeline notes and submitted forms'), which is redundant padding.

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 output schema, the description carries the burden of describing returns, and it does list the entry types and ordering. Auth requirements are stated; only pagination behavior beyond 'limit' and full return shape are left implicit.

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%, so both parameters are already documented, giving a baseline of 3. The description adds a small amount of meaning by tying 'limit' to the 'latest few visits before a booking' scenario, but no format or edge-case detail beyond the schema.

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+resource ('Get client timeline') and enumerates exactly what entries it returns (appointments, sales, timeline notes, form submissions), so an agent knows what it does. It scopes to 'one client' but never explicitly distinguishes itself from siblings like mangomint_list_appointments or mangomint_find_client.

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?

Offers one concrete use case ('Use limit to read the latest few visits before a booking'), which implies when to reach for it, but gives no explicit when-not guidance or named alternative for retrieving the same data another way.

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