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

The annotations already mark the operation as read-only, open-world, and idempotent, and the description adds valuable behavioral context: timezone handling, live meeting types from the scheduler, the ~30-minute consultation duration, and the one-day-notice rule that makes the search start tomorrow. No contradiction with annotations.

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?

Four tight sentences front-load the purpose and sequencing, then add only the essential behavioral and routing context. Every sentence earns its place and no schema content is duplicated.

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 6-parameter, nested-object tool with no output schema, the combination of this description and the richly described schema fully equips an agent to call it correctly. It covers the scheduling flow, defaults, routing, formats, and timezone behavior. No critical gap remains.

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 the baseline is 3, but the description adds meaning beyond the schema by explaining that meeting types route to the right person, that general-inquiry is the default, and that timezone should be the person's own. It complements rather than repeats the schema descriptions.

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 a specific verb and resource: 'List open times on Upforge's calendar for a free consultation' and immediately distinguishes it from book_consultation by stating it should be called first. The title reinforces this without ambiguity.

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?

It explicitly says to call this before book_consultation, to let the person pick a time, and never to pick one for them. It also clarifies meeting-type routing and the default general-inquiry behavior, leaving no doubt about when this tool is the right choice.

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