get_booking

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

No annotations are provided, so the description carries full burden. It only states 'Retrieve... by its ID' without disclosing behavior on missing IDs, authentication requirements, or any side effects. The existence of an output schema partially mitigates this for return values, but other behaviors remain opaque.

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 sentence of 8 words with no filler. Every word is necessary and front-loads the purpose. It is highly concise and well-structured.

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's simplicity (one parameter, no nested objects, output schema present), the description is mostly complete. It covers the core action and selection criteria. Usage context and behavior details are lacking, but the tool is straightforward enough that this may be acceptable.

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?

The input schema has 100% coverage for the single required 'id' parameter, but its description is missing (0% schema coverage). The tool description adds only 'by its ID', which does not enhance meaning beyond the schema. However, the parameter is a straightforward integer identifier, so minimal additional semantics are needed.

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 verb 'Retrieve', the resource 'ChurchSuite booking', and the criteria 'by its ID'. This distinguishes it from sibling tools like list_bookings (which returns multiple) and find_next_booking_* (which search by criteria).

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 implies usage when you have a specific booking ID, but does not explicitly state when to use this tool versus alternatives (e.g., list_bookings or find_next_booking_by_name). No exclusion criteria or alternative tool names are mentioned.

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