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

Annotations only supply destructiveHint=true; the description adds the essential context: required permission scope, that the change runs immediately with no enforced approval step, that a blank location is a destructive clear rather than a no-op, and the partial-date hazard. That is materially more than the annotation conveys.

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?

Purpose is front-loaded in the first clause, followed by permission, execution semantics, and the destructive/hazard notes. No filler sentences; every clause carries a fact an agent needs.

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 7 params, a nested employee object, no output schema, and a destructive mutation, the description covers auth, immediacy, clearing behavior, and the date hazard. It leaves unspecified whether omitted fields are preserved and what the response contains, but overall it is sufficient to call safely.

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 43%, so the description must compensate, and it does for the riskiest parameters: it explains that location=blank clears the field and that start/end times must be cross-checked against the existing meeting before a single-ended change. meetingTypeId and title remain undocumented here, which keeps it from a 5.

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?

States a specific verb ('Reschedule or edit') and resource ('meeting details'), which cleanly separates it from create_meeting and the get/list siblings. It does not name siblings explicitly, but the instruction to 'read the existing meeting' implicitly routes to builderprime_get_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?

Gives concrete preconditions ('meetings.edit required') and a procedural rule: read the existing meeting before changing only one of start/end. It does not state when-not-to-use or name an alternative tool, so it falls short of a 5.

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