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

Goes well beyond the annotations by disclosing what changes (customer Revenue To Date and Unpaid Balance), the no-card-charge constraint, the per-call confirmation default and its toggle, human-in-the-loop guidance, and the required Cotlet API key scope. This is exactly the mutation/auth/side-effect context annotations don't carry.

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 readable, but the no-charge point is repeated three times ('Does not charge a card', 'It never charges the card on file', 'Appointments paid by card cannot be changed this way'), which dilutes an otherwise tight description.

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 single-parameter mutation with no output schema, the description covers side effects, confirmation behavior, exclusions and auth requirements. Nothing essential to calling it correctly is missing.

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?

Only one parameter and schema coverage is 100%, so the schema already documents appointment_id and points to list_appointments. The description adds no additional parameter semantics, which meets the baseline for a fully-covered 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 and resource — recording an offline (cash/Venmo/PayPal) payment that marks one appointment as paid — and clearly distinguishes itself from sibling tools like zenmaid_list_appointments or zenmaid_create_appointment. An agent can tell what it 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?

Explicitly scopes usage to offline payments and states a clear exclusion: 'Appointments paid by card cannot be changed this way' plus 'Does not charge a card.' It gives condition-based guidance but never names a sibling alternative for the card-payment case, so it stops short of a 5.

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