list_appointments

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only vaguely references filtering and pagination without explaining what happens when no filters are applied, what the default result set looks like, authentication requirements, or rate limits.

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 two-sentence structure is appropriately front-loaded with the primary action. It wastes no words, though its brevity borders on under-specification rather than efficient conciseness given the lack of supporting annotations or output schema.

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?

Given the absence of annotations and an output schema, the description should provide richer context about return values, result structure, or default behaviors. As written, it is insufficiently complete for a 6-parameter tool with no other behavioral metadata.

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%, establishing a baseline of 3. The description mentions 'filtering and pagination' which conceptually maps to the parameters but adds no specific semantic details—such as date format specifics or that locationId defaults to an environment variable—that aren't already explicit in the schema definitions.

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 the basic action (list) and resource (appointments) clearly, including the system context (Shopmonkey). However, it fails to differentiate from the sibling tool 'get_appointment', which presumably retrieves a single record by ID versus this tool's bulk listing capability.

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?

The description mentions 'Supports filtering and pagination', which loosely implies when filtering is needed, but provides no explicit guidance on when to use this tool versus 'get_appointment' or other alternatives. No prerequisites or exclusions are stated.

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