trmnl_delete_room_booking_collection

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds genuine consequence detail the annotations cannot: the collection is removed from every device while the underlying calendars survive. 'Changes remote state' reinforces the openWorld write. This is real value beyond structured fields, though it stops short of mentioning irreversibility or auth requirements.

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 destructive consequence is front-loaded in the first two sentences, which is exactly right. A couple of sentences ('Changes remote state or starts work') are boilerplate filler, keeping it just under top marks.

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 two-parameter destructive delete with no output schema, the description covers what is removed, what persists, and the endpoint. The main gap is lack of return/error behavior and confirmation of what happens to devices afterward, but the essential picture an agent needs is present.

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 50% and the path parameters (installation_id, id) are already described in the schema. The description embeds the endpoint template, implicitly mapping {installation_id} and {id} to the path object, but adds no new semantic detail about the profile parameter or id format beyond the schema.

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 ('Remove a calendar collection') and immediately clarifies scope with 'Takes it off every device.' This lets an agent distinguish it from the create/update/bind collection siblings without opening any 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?

'Run only within the user-authorized scope' is a generic safety caveat rather than real routing guidance. It doesn't say when to delete vs. update or unbind, nor what prerequisites (e.g., collection emptied) apply. Usage is only implied by the verb.

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