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 genuinely new context: the precise return payload (appointments, notes, memberships, packages, gift cards, points) and an auth requirement ("Needs the user's Cotlet API key with access to this app").

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 first two sentences restate the same payload list verbatim ("Client profile with upcoming appointments..." / "Returns one client profile with upcoming appointments..."), wasting space. The usage and auth sentences are valuable, but the duplication costs it.

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 correctly carries the burden of describing return contents, which it does in detail, plus the auth prerequisite. Only the relationship to the find_client lookup step is left unaddressed for a single-required-parameter read tool.

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% and the schema itself says the ID comes "from find_client." The description adds nothing about client_id, so the baseline of 3 applies — the schema does all the parameter work.

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 (get) and resource (client) and enumerates the profile contents, so the agent knows exactly what it retrieves. It does not, however, differentiate itself from the sibling meevo_find_client, which is the natural source of the required client_id.

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?

"Use it before booking or selling, so your agent sees what the client already owns" gives a concrete when-to-use condition tied to the booking/selling siblings. It stops short of naming meevo_find_client as the prerequisite lookup step or stating when a plain client lookup is unnecessary.

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