trmnl_list_room_booking_integrations

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds useful context about what the listing contains (connected accounts plus selected-calendar counts) but says nothing about pagination, filtering, or missing-integration cases.

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, but the second sentence is a fragmented run-on ('with how many of their calendars are selected for sync. integration_type and id address one in the other integration operations.') and the raw endpoint path adds little 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 read-only listing tool with strong annotations and no output schema, the description covers what is returned (accounts/workspaces and calendar sync counts) and the API route. It is sufficient to call correctly, with only pagination/error behavior left implicit.

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?

Both parameters (installation_id and profile) already have schema descriptions; the description adds nothing about them. Mentioning integration_type/id clarifies downstream usage but those are not parameters of this tool, so parameter semantics remain at the schema-supplied baseline given 50% coverage.

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?

The first line states a specific verb and resource ('List the connected calendar accounts') and the follow-up clarifies that these are Google/Microsoft accounts and workspaces tied to the installation, with calendar sync counts. That distinguishes it from the nearby trmnl_list_room_booking_calendars, though the sibling contrast is implied rather than stated.

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 note that 'integration_type and id address one in the other integration operations' hints at how this list feeds downstream tools, but there is no explicit when-to-use or when-not-to-use guidance, and no alternatives such as trmnl_list_room_booking_calendars are named.

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