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

Annotations already cover the safety profile (readOnly, non-destructive), and the description adds genuinely useful context: private notes are visible only to owner and office manager accounts, and a Cotlet API key with app access is required. It also states the appointment ordering ('newest first'). It does not mention pagination or error behavior for a missing contact.

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 with purpose, then return fields, then the access caveat. The opening sentence ('One contact with notes, custom fields, and past and upcoming appointments') partially duplicates the more detailed second sentence, but overall it is tight and earns its length.

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 return-value burden and does so thoroughly (field list, note visibility rules, ordering), plus the auth prerequisite. An agent has everything needed to call it and interpret the result.

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 single parameter's description already says 'Contact ID from list_contacts'. The description adds no further syntax or format detail, so this is the baseline 3 where the schema carries the load.

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 ('get one contact') and enumerates the payload: addresses, notes, custom fields, revenue, balance, appointments. It is clearly distinct from zenmaid_list_contacts by emphasizing 'one contact', though it never names that sibling explicitly.

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?

Usage is only implied by the singular framing and the 'Contact ID from list_contacts' schema hint. There is no explicit statement of when to prefer this over zenmaid_list_contacts or what to do when an ID is unknown.

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