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

readOnlyHint=true already tells the agent this is a safe read; the description adds the field set returned and the underlying endpoint (GET /appointment). It says nothing about pagination limits, default ordering, or result size — which matter for an 8-param list call — so added value is modest.

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?

Two short sentences, front-loaded with the operation and its returned shape, followed by the API mapping. Nothing redundant or padded.

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 8 optional params, full schema coverage, no output schema, and safety covered by annotations, the description supplies the one thing the schema lacks: what the objects contain (time window, job, location, technicians). It omits pagination/ordering behavior, a minor gap.

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 every filter (page, limit, jobId, techIds, windowBeginsAfter/Before, status, locationId) is already documented, and the baseline 3 applies. The description adds no format detail beyond the schema, only confirming the filterable dimensions.

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?

Specific verb + resource ('List scheduled appointments') plus a parenthetical clarifying what an appointment is (technician visits) and which fields come back. It implicitly contrasts with the singular get_appointment sibling via 'List', but never names it 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?

The description implies bulk retrieval of appointments with filters, but never states when to use this versus servicetrade_get_appointment for a single record, nor when to prefer filtering by jobId vs techIds. Usage must be inferred from the tool name and schema.

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