calmesh_list_bookings

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states that the tool returns booking details including visitor info and status, and requires 'book' scope, which are useful operational traits. It does not explicitly say it is read-only, but 'list' implies a non-mutating operation.

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, efficient sentence that conveys purpose, return contents, and scope requirement without any fluff. It is front-loaded with the primary verb and resource.

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 simple list tool with no output schema, the description covers the essential points: purpose, optional filtering, return data contents, and authentication scope. It does not specify response format or pagination behavior beyond the parameter descriptions, but this is adequate given the tool's simplicity.

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 100% with all three parameters having descriptions. The description adds nominal value by labeling the parameters as 'pagination and filtering', which contextualizes limit/offset and stakeholder_id, but does not significantly augment the schema's own clear documentation.

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 uses a specific verb and resource ('List bookings') and explicitly mentions optional pagination and filtering, distinguishing it from sibling tools like create_booking, cancel_booking, and list_calendars. The return details (visitor info, status) further clarify its purpose.

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 description provides clear context for when to use this tool (listing bookings with pagination/filtering) and notes the required 'book' scope. It does not explicitly mention alternatives or when not to use it, but the usage scenario is evident.

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