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

Annotations already declare readOnly/openWorld/non-destructive, and the description adds genuinely useful context beyond them: the auth requirement (Cotlet API key with app access) and the fact that results come from the Appointment Book's Waitlist section. No contradiction with annotations.

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-loads what the tool returns, then adds workflow and auth notes in compact sentences. Slightly listy but every sentence carries information.

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 names the returned fields and the source section, and it covers auth and the follow-up action. Adequate for a simple read-only list tool.

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 optional 'date' parameter is documented in the schema; the description's mention of 'preferred dates' refers to returned fields rather than the filter, so it adds no parameter meaning beyond the schema. Baseline 3.

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+resource (list waitlist entries) and enumerates the returned fields (client, requested services, preferred employee/dates, comment). It is unambiguous within the DaySmart toolset, though it does not contrast with other waitlist tools in sibling apps.

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?

Provides workflow guidance ('Pass waitlist_entry_id to book_appointment to convert an entry'), which implies why one would list waitlist entries, but gives no explicit when-to-use vs when-not or alternative listing tools.

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