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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the description only needs to add operational context — which it does, disclosing the underlying endpoint (GET /appointments) and the record fields returned. It does not mention ordering, totals, or behavior at the last page, leaving a small gap.

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?

A single front-loaded sentence carries the filter semantics and returned fields, with the endpoint appended as a compact implementation hint. No redundancy with the title or 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?

With no output schema, the description usefully enumerates the returned fields and states the filter scope, which is enough to call the tool correctly. It stops short of describing result volume, ordering, or the total-count/next-page signal an agent might need to paginate.

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; the description earns a bump by glossing 'open' as 'upcoming' and enforcing the 'one filter per call' constraint, which the enum alone does not convey. Page-size behavior is left entirely to the schema, which is acceptable given full coverage.

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 ('List appointments') plus the scope of what can be listed (open vs. complete) and the fields returned ('title, time, location and creator'). An agent can distinguish this from freshsales_get_appointment (single record) and freshsales_create_appointment without opening any schema.

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?

Clarifies that open means upcoming and complete means past, so the agent knows which filter value matches intent, and the 'one filter per call' note signals that both statuses require two calls. It stops short of naming an alternative (e.g., the generic freshsales_search) for filtering by title, creator, or date.

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