list_booked_resources

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

With no annotations, the description does not disclose behavioral traits. It hints at optional filtering but does not mention pagination (page, per_page parameters) or whether the output is sorted, limited, or includes any context about the response structure. The tool's behavior around empty or invalid booking IDs is also not addressed.

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 description is a single, well-structured sentence that communicates the core action and key filter option without redundancy. It is front-loaded and every word adds value.

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?

Given the tool has 3 parameters, no annotations, and an output schema, the description is incomplete. It does not mention pagination, return structure, or the behavior when no booking ID is provided. More context is needed for effective use.

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 description coverage is 0%, so the description must explain parameter semantics. It only mentions 'filtered by booking ID' for booking_ids, but completely ignores page and per_page parameters, leaving their purpose and defaults ambiguous.

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 description clearly states the tool lists resources booked against ChurchSuite bookings, with optional filtering by booking ID. This specific verb+resource combination distinguishes it from sibling tools like list_resources (general resources) and list_bookings (listings of bookings).

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?

No guidance is provided on when to use this tool versus alternatives such as list_bookings or list_resources. The description lacks any indication of when filtering is recommended or when the unfiltered output might be too broad.

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