Get available inventory

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

Discloses a key behavior: never returns protected/booked/blocked inventory. However, with no annotations provided, it fails to mention auth requirements, rate limits, or behavior when no inventory matches (e.g., empty result set).

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 focused sentences with no redundant information. Purpose is stated first, followed by a critical behavioral constraint. Every sentence 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?

For a 5-parameter tool with no output schema and no annotations, the description is severely incomplete. It omits return values, error handling, pagination, and parameter details, leaving the agent to guess or fail.

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 has 5 parameters with 0% description coverage (no descriptions in schema). The description only vaguely references 'preferred time', failing to explain each parameter's purpose, constraints, or expected values. The agent receives no guidance on how to use parameters.

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?

Description clearly states it finds available tee times near a preferred time and explicitly mentions it never returns non-bookable inventory. This differentiates it from sibling tools like check_booking_action or create_soft_hold.

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?

Implied usage for finding available tee times, but no explicit when-to-use, when-not-to-use, or comparison to alternatives like get_course_context. Missing guidance on prerequisites or if inventory availability may be delayed.

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