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

Annotations already declare destructiveHint=true, openWorldHint=true and non-idempotency, but the description adds real side-effect disclosure the annotations cannot convey: creating a meeting texts the contact, moving a meeting re-sends its texts, status "done" completes the item, and Google Calendar syncs both ways. The only gap is that it never says what the call returns or whether a delete is reversible.

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?

Everything is front-loaded into a single dense sentence with per-action parentheticals, and no clause is filler. The nesting of semicolons inside parentheses makes it harder to parse than it needs to be, but the information density is earned.

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 an 18-parameter multi-action mutation tool with no output schema, the description covers the risky branches — meeting texts, series scope, Google removal — which is where an agent is most likely to err. Missing is how to obtain the id required for update/delete and how this tool relates to meetings_book for scheduling.

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 already 89%, so baseline is 3, and the description still adds semantic weight on top: it explains that status "done" is a completion rather than a label change, that contactId/companyId/dealId act as relinks, and it reinforces the scope/remove_from_google conditions. It doesn't touch the remaining fields (notes, location, color), which the schema already documents well.

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?

Opens by naming the resource precisely — tasks, events and meetings, explicitly mapped to 'the Calendar page in the apps' — then enumerates the three verbs (create/update/delete) with per-action behavior. An agent can distinguish this from tasks_list without opening a schema, though the description never names the sibling it contrasts with.

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 conditional rules: ask first before texting a contact on meeting creation, confirm before delete, remove_from_google only if the user says, repeating tasks need a scope. It stops short of routing to alternatives — notably meetings_book for scheduling and tasks_list for finding ids — so the agent must infer those boundaries.

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