calmesh_get_slots

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

With no annotations, the description carries the burden of disclosing side effects and requirements. It mentions the "book" scope and that it returns visitor-bookable time slots, implying a read-only operation. However, it doesn't state whether it modifies data, handle timezone logic fully, or describe error conditions.

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?

Two sentences, front-loaded with the action and resource. Every word adds value, with no redundancy or filler.

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?

The tool is relatively simple (3 params, no output schema). The description covers purpose, return value, and auth requirement. It could be more detailed about edge cases, but for its complexity, it's sufficiently complete.

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 100%, so the schema itself defines all parameters clearly. The description adds minimal additional meaning beyond naming the booking page and date. It doesn't explain timezone behavior or input format nuances beyond the schema.

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 gets available booking slots for a booking page on a specific date, using a specific verb-resource pair. This distinguishes it from siblings like check_availability, which focuses on broader availability checks.

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 specifies the context (booking page, date) and the required scope ("book"), giving clear guidance on when it's appropriate. It does not explicitly exclude alternatives or name sibling tools, but the use case is unambiguous.

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