trmnl_refetch_room_booking_calendar

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true; the description adds real value by explaining the effect (source is read, mirror is updated) and cautioning that it changes remote state or starts work. It does not say whether the refetch is async, what happens on failure, or what is returned, 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?

Effect and mechanics are front-loaded in two tight sentences. The trailing 'Changes remote state or starts work. Run only within the user-authorized scope.' is generic boilerplate that adds little, but the whole is not bloated.

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?

With no output schema, the description should say what a refetch yields (job id, updated mirror, immediate result), and it doesn't. It covers what the tool does and its mutation surface, but leaves the outcome and the meaning of the nested path parameters under-specified for a non-idempotent, open-world operation.

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 description mentions no parameters at all. It never tells the agent that installation_id identifies the room-booking installation, that id is the calendar, or what the profile parameter selects, so it does not compensate for the 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?

Specific verb (refetch) plus resource (calendar) and scope (from its source), and it explains the effect: reading the source calendar and updating the mirror the screens show. That clearly separates it from get_room_booking_calendar (read config) and update_room_booking_calendar (mutate settings).

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?

The 'now' and 'Run only within the user-authorized scope' phrasing implies this is an immediate, manual refresh, but it never says when to prefer it over trmnl_sync_room_booking_integration or trmnl_start_refresh, nor what preconditions must hold. Usage is inferable but not explicit.

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