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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds the concrete endpoint GET /appointments/{id} and, more usefully, that attendees are included in the result — a return-shape detail not available elsewhere since there is no output schema. It says nothing about behavior for a nonexistent or inaccessible id.

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 terse sentences, front-loaded with the outcome, then the endpoint. Nothing is padded and nothing repeats the title verbatim.

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?

For a one-parameter read-only tool with no output schema and full annotation coverage, the essentials are present: what comes back (appointment plus attendees) and which route it hits. Only the failure case for an invalid id is missing.

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% and there is a single documented parameter (appointment_id, positive integer), so the schema carries the load. 'by id' adds no syntax, format, or sourcing hint (e.g., where to obtain the id) beyond what the schema states.

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 names a single specific resource and scope: 'One appointment by id with its attendees,' which implicitly separates it from the sibling freshsales_list_appointments and freshsales_create_appointment. It never names those siblings explicitly, so the differentiation is inferential rather than stated.

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?

'by id' implies you need a known appointment id, which implies the alternative (list/search/lookup) when you don't have one, but the description never says that. No exclusions or alternative routing are given despite freshsales_list_appointments, freshsales_search and freshsales_lookup all being plausible overlaps.

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