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 value beyond them by disclosing the auth requirement (a Cotlet API key with access to this app) and the scope of results (every location in the account). It does not describe ordering or pagination, but for an unfiltered list of a small collection that is minor.

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?

Four short sentences, front-loaded with what is returned before the usage and auth notes. The redundant 'Mangomint:' prefix and the fragment-style first sentence cost a little, but there is no wasted content.

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 parameters, no output schema, and annotations covering the safety profile, the description supplies everything an agent needs: what comes back, the key field (location_id) and how it feeds other tools, plus the auth prerequisite. Only a note on result ordering or paging would add anything.

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, so there is nothing for the description to clarify and the baseline is 4. The empty schema is consistent with the description's claim that it returns every location without filtering.

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 ('Your business locations') and enumerates the returned fields (address and time zone), so an agent immediately knows what this tool retrieves. It is the only location-listing tool in the Mangomint family and is not confusable with list_appointments, list_services, or list_waitlist.

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 concrete downstream guidance: 'Use the location_id from each item in the other tools,' which tells the agent why and when to call this. It also notes that most single-location businesses have one item, setting expectations about result size. There is no explicit when-not-to-use statement, but no competing sibling exists to route away from.

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