business_schedule_meeting

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

No annotations exist, so the description carries the full burden of behavioral disclosure. It says 'propose or schedule' but does not clarify whether invitations are actually sent, whether the calendar is modified, or what role the default preview_only=true plays. The phrase 'calendar response tracking guidance' hints at tracking behavior but does not explain what the tool does with responses.

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 one sentence with no redundant filler. However, it is under-specified rather than appropriately concise, and the phrase 'with calendar response tracking guidance' is vague and poorly structured.

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 seven optional parameters, no annotations, and 0% schema coverage, the description is far too thin to support correct invocation. It does not explain the proposal-vs-booking distinction, preview behavior, attendee encoding, or when to prefer sibling meeting tools. The presence of an output schema mitigates return-value explanation but not the other gaps.

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 0%, yet the description explains none of the seven parameters. Critical semantics such as preview_only defaulting to true, attendees being a JSON-string-like value, time_window format, and duration_minutes are completely undocumented. The description adds no value beyond what the bare schema already exposes.

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 names a specific resource (meeting) and verbs ('propose or schedule'), so it is not a tautology. However, the dual verbs create ambiguity about whether the tool actually books a meeting or merely proposes one, and 'calendar response tracking guidance' is vague. It also does not distinguish this tool from sibling scheduling tools like crm_propose_meeting_slots or crm_book_meeting.

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?

There is no guidance about when to use this tool versus alternatives. The description provides no context, prerequisites, exclusions, or selection criteria. Given many sibling tools around meetings and scheduling, an agent cannot determine whether this is the right tool.

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