get_appointment

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

No annotations provided, so description carries full disclosure burden. Adds 'detailed information' to distinguish depth from summary listings, but fails to disclose read-only safety (implied but not stated), error behavior if ID invalid, or authorization requirements.

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?

Single sentence of 9 words. Front-loaded action verb, zero redundancy, every word earns its place. Appropriate length for simple retrieval operation.

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?

Adequate for a simple 1-parameter retrieval tool without output schema. Describes the lookup mechanism and depth of return ('detailed'). Could improve by noting error behavior (e.g., 404 if ID not found) but satisfies core requirements.

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% with 'id' parameter fully described as 'The appointment ID'. Description mentions 'by its ID' confirming the parameter's identifying purpose, but adds no syntax guidance or validation rules beyond schema. Baseline 3 appropriate for high schema 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?

Excellent clarity: specific verb 'Get', resource 'appointment', and scope 'single appointment by its ID' clearly distinguishes from sibling list_appointments (plural listing) and update_appointment (mutation).

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 implied usage through 'by its ID', signaling this requires a specific identifier rather than browsing. However, lacks explicit contrast with list_appointments alternative or guidance on when to use each (e.g., 'Use this when you have a specific appointment ID; use list_appointments to search broadly').

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