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

Annotations only cover read/write/open-world/destructive flags; the description adds real behavioral context the annotations cannot convey — the note is staff-visible but not client-visible, note_type must pre-exist at the location, each call is confirmed by default, and the action reaches other people. Return format is not described, so it falls short of 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?

The core constraints are front-loaded and dense, but the first two sentences restate the same thing ('Add an internal visit note to a client profile' / 'Adds an internal visit note to a client profile'), which is pure duplication and one wasted sentence.

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 simple 3-parameter write with a fully covered schema and no output schema, the description covers visibility semantics, the note_type prerequisite, confirmation behavior, and auth requirements — everything an agent needs to call it safely. Only minor gaps remain (e.g. what a successful response contains).

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 the schema already documents all three parameters (including 'Client ID from find_client' and 'as set up at your location'). The description's only added nuance is the color-formula example and the reinforced note_type constraint, which is marginal — baseline 3 applies.

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 and resource (add an internal visit note to a client profile) and immediately scopes it with an example (color formula), so an agent can distinguish it from meevo_book_appointment, meevo_get_client, and other Meevo siblings without opening a 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?

Gives clear preconditions: note_type must be one configured at the location, and the API key needs access to this app. It also implies usage context (internal staff-facing notes). It stops short of naming an alternative tool or stating when not to use this one, but no Meevo sibling competes directly.

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