trmnl_sync_room_booking_integration

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

Annotations declare readOnlyHint=false, openWorldHint=true and non-idempotent, and the description is consistent with that: it hits the provider, 'Changes remote state or starts work,' and is scoped to user authorization. It adds real context beyond the annotations (external provider call, effect on the calendar list) but says nothing about failure modes or repeat-call behavior.

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 purpose is front-loaded in the first line, but the raw 'TRMNL POST /api/apps/...' endpoint line and the duplicated 'Refresh the calendar list' / 'Reads the calendars' framing add noise without new meaning for an agent.

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 non-idempotent, open-world mutation with nested parameters and no output schema, the description covers the what and the effect on listRoomBookingCalendars but omits return shape, error/permission conditions, and any guidance on the nested path fields. Adequate but with clear gaps.

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 only 50% and the nested path object's integration_type has no description at all. The description never mentions installation_id, integration_type, id, or the profile parameter, so it does not compensate for the coverage gap or explain how integration_type selects behavior.

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 ('Refresh the calendar list of a connected account') and adds the downstream effect ('so a new room shows up in listRoomBookingCalendars once selected'). This distinguishes it reasonably from list/refetch siblings, though it never names an alternative tool directly.

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?

Implies the trigger context (after connecting an account, to pick up newly visible rooms) and warns 'Run only within the user-authorized scope.' However, it does not say when to prefer this over sibling tools like trmnl_refetch_room_booking_calendar or trmnl_list_room_booking_calendars, leaving the choice to inference.

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