trmnl_cancel_public_booking

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 genuinely new behavioral context: no bearer-token auth is required, and the target must be a TRMNL-sourced booking that has not yet started. It still does not say whether the cancellation is reversible or what the response contains, and 'Changes remote state or starts work' largely restates the annotations.

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?

Front-loaded with the action and the endpoint/auth facts, which is good, but the final line ('Changes remote state or starts work. Run only within the user-authorized scope.') is generic boilerplate that duplicates the destructive annotation without adding information.

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 destructive, no-output-schema mutation, the description covers auth mode, precondition (not started, TRMNL-created), and the underlying REST call, which is most of what an agent needs to invoke it safely. Missing are post-call effects (reversibility, effect on the room calendar/screens) and any mention of the profile parameter.

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 schema already describes 'id' and 'token' individually, so the description's main added value is mapping them into the endpoint template 'DELETE /api/book/{token}/bookings/{id}'. It says nothing about the 'profile' parameter or about id/token format expectations beyond the schema, so it neither compensates for nor exceeds the moderate coverage gap.

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 ('Cancel an upcoming public booking') with the additional constraint that it only applies to TRMNL-created bookings that have not started. It does not explicitly differentiate from the sibling trmnl_end_public_booking or trmnl_cancel_room_booking, so an agent must infer which cancel/end variant fits.

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 an explicit usage boundary: 'Public: no bearer token' and 'Only a booking made through TRMNL that has not started,' which tells the agent when this tool applies and when it does not. It never names the alternative tools (end vs cancel, room booking vs public booking) that should be used when those preconditions fail.

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