Get appointment details

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

No annotations provided. The description conveys it is a read operation fetching details of a confirmed appointment, but does not disclose additional traits like permissions, side effects, or error scenarios. It adds value over no description but lacks depth.

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 sentences, front-loaded with capability, no filler. Second sentence provides usage guidance. Every sentence adds value.

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 tool with one parameter and no output schema, the description lists the returned data and usage context. It is adequate, though it could mention error cases or confirm the appointment must be 'confirmed'.

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% with a good description for appointment_id. The tool description adds minimal extra meaning, reinforcing the parameter's source. 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?

The description explicitly states 'Pull full briefing on a specific confirmed appointment' and lists the data returned (contact info, BANT, etc.). It clearly distinguishes from siblings 'book_appointments' and 'check_status'.

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 description says 'Use when the user wants to prep for a specific meeting,' which is a clear when-to-use. It does not explicitly mention alternatives, but the sibling context provides that.

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