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

Annotations already indicate destructiveHint=true, but the description adds the concrete external side effect: 'HubSpot sends them the invitation and the calendar event'. It also discloses the consent gate and the prohibition on fabricating details, which goes beyond annotation coverage.

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 sentences, each earning its place: the action, the external side effect, and the key precondition. No filler, with important constraints front-loaded.

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?

With a full input schema, output schema present, and annotations covering destructive/read-only behavior, the description supplies the missing operational context: when to book, what happens externally, and the consent condition. Nothing needed for correct invocation is omitted.

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%, and the schema already explains startTime as returned by get_demo_availability, durationMinutes as the matching value, and consent's exact requirement. The description mostly restates these constraints; the only novel bit, 'never invent their details', is more behavioral than parameter-specific.

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 opens with 'Book a time on the Tabflows demo calendar', naming a specific action and resource. It also ties the call to availability from get_demo_availability, distinguishing it from sibling tools like get_demo_booking_link or fetch.

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?

Explicit guidance: 'Only call this after the person has chosen the time and agreed to Tabflows contacting them at that email; set consent to true only then'. This gives a clear precondition and when-not-to-call instruction, plus 'never invent their details'.

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