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

Adds real information beyond the destructiveHint annotation: the write is immediate and triggers vendor notifications, which matters for a non-idempotent mutation. It still doesn't say whether the created meeting can be rolled back or what identifier comes back, so not a 5.

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 front-loaded sentences with no filler; the side-effect warning sits where an agent will see it before composing arguments. 'meetings.create required' is terse jargon that costs a little clarity for its brevity.

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 7-parameter destructive mutation with no output schema and only 43% schema coverage, the description covers side effects and preconditions but omits what the call returns (meeting id?) and how to resolve meetingTypeId or clientOpportunityId. Adequate, not complete.

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%, below half, so the description needs to compensate — it doesn't. It names 'dates, timezone, attendee and type', but timezone is not a parameter at all (dates are epoch milliseconds per the schema) and clientOpportunityId, title and meetingTypeId receive no explanation, leaving several required fields unexplained in both places.

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 and resource ('Create a meeting') plus the scope ('for a client opportunity'), which cleanly separates it from builderprime_update_meeting and the project siblings. An agent can identify the operation without inspecting the schema.

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?

'Confirm dates, timezone, attendee and type before calling' gives a concrete pre-flight checklist, and 'meetings.create required' signals a permission prerequisite. It stops short of naming when not to use this versus builderprime_update_meeting, so it lands just below the top mark.

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