conduyt_get_appointment

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

No annotations exist, so the description carries the full burden. It discloses the returned data shape (contact, assignee, booking page, notes) and implies a read-only lookup via 'Get', but says nothing about permissions, scoping to the caller's account, or not-found behavior.

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?

One sentence, front-loaded with the verb and resource, with the returned field summary attached compactly. No filler.

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 simple one-parameter read tool with no annotations or output schema, the description compensates by enumerating the key returned fields, which is the most useful thing it can add. Missing only error/not-found behavior.

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 'id' parameter is documented as an 'Appointment UUID' in the schema itself. The description adds nothing about the identifier (e.g., where to obtain the UUID), so baseline 3 is appropriate.

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 ('Get a single appointment') with 'single' signaling retrieval-by-id rather than a list. It doesn't name the sibling it contrasts with (conduyt_list_appointments), but the scope is unambiguous.

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 word 'single' implies this is the lookup-by-id path versus the list tool, but there is no explicit when-to-use statement, no mention of conduyt_list_appointments as the alternative, and no note about what happens if the appointment doesn't exist.

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