appointments_create

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

No annotations are provided, so the description carries the full burden. It discloses the auto-population behavior when linking to a ticket, which is a useful behavioral trait. However, it does not mention other side effects, permissions, or constraints beyond that.

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?

The description is two sentences long with no fluff. It is front-loaded with the core purpose and immediately provides a key usage hint.

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?

Given the tool has 14 parameters, no required parameters, and no output schema, the description is minimal. It only highlights one feature (ticket link). While the schema covers all parameters, the description lacks guidance on typical usage, optionality, or combination of parameters, making it somewhat incomplete for a complex tool.

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 baseline is 3. The description adds value beyond the schema by explaining that ticket_id auto-populates description and location, which is a meaningful semantic enhancement for that parameter. Other parameters are not enriched, but the added context for ticket_id lifts the score slightly.

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 clearly states 'Create a new appointment' which is a specific verb and resource. It distinguishes from sibling tools like appointments_list, appointments_delete, etc., by the verb 'Create'.

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 provides guidance on when to use the ticket_id parameter ('when possible, link to a ticket') and explains the benefit (auto-population). However, it does not provide explicit when-not-to-use or alternatives like scheduling_create.

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