Book a call/demo with a CRM contact

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

Adds value beyond annotations by describing validation (company exists, contact belongs) and storage behavior (crm/bookings.json, status 'scheduled'). Annotations are non-contradicting.

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?

Three concise sentences, front-loaded with purpose, then validation, then storage details. No wasted words.

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?

Good coverage given complexity: explains workflow, validation, and storage. Missing return value info, but acceptable since output schema not provided. Sufficient for a booking 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?

Explains 'company' and 'contact' validation relationship and 'at' as ISO timestamp. Schema coverage is 50% but description partially compensates. Other parameters (type, notes, subject, durationMins, project) are not clarified.

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?

Description clearly states it schedules calls/demos/meetings with a CRM company and optional contact. It distinguishes from siblings like list_bookings and cancel_booking, but does not explicitly differentiate.

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 when to use (scheduling) and mentions validation steps, but lacks explicit when-not-to-use or alternative tools. Context is implied but not explicit.

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