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

Annotations already cover readOnly/openWorld/destructive, but the description adds genuinely new behavior: results are ordered earliest first, the Appt Result field is empty until someone sets it, and it requires a Cotlet API key with access to the app. These are useful operational details beyond the annotation set.

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 resource is front-loaded and the description is compact, but the opening fragment 'Sales appointments in a date range with...' is largely restated by 'Lists sales appointments between two dates,' creating mild redundancy. Still efficient overall.

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 usefully enumerates the returned fields, states the sort order, and notes the auth requirement, which is enough for an agent to call it correctly. Minor gaps like pagination behavior remain unaddressed.

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%, so the baseline is 3, but the description adds meaning beyond the schema by explaining what 'Appt Result' is and why unresulted_only selects the visits still needing it ('Result is empty until someone sets it'). This clarifies the domain concept rather than merely restating the field.

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+resource: 'Lists sales appointments between two dates,' and enumerates the fields carried (contact, salesperson, set by, Appt Result). This distinguishes it from sibling list tools like marketsharp_list_jobs and marketsharp_list_activities, though it doesn't explicitly name an alternative.

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 implied by the date-range framing, and 'Set unresulted_only to see the visits that still need an Appt Result' gives some conditional guidance. However, there is no explicit when-to-use vs when-not or a named alternative, so the routing guidance remains implicit.

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