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

The description implies a read-only operation by focusing on inventory availability and terms, and the annotations (readOnlyHint, idempotentHint, destructiveHint) reinforce that there are no side effects. No contradictions are present, though explicit mention of being read-only would have been slightly clearer.

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, concise sentence that packs all key information: current availability, upcoming groups by ready date, and ordering terms. There is no redundant or extraneous content, making it well-structured and easy to parse.

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?

While the description covers the main content (inventory and terms), it does not explain what 'teens' or 'flip' mean, nor does it specify the output format or any additional details like pricing or group sizes. Given the domain-specific nature and lack of an output schema, this leaves some gaps in agent understanding.

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?

There are zero parameters, so the description has no obligation to describe parameter inputs or outputs. The baseline for no parameters is 4, and the description adequately introduces the data it returns without needing to explain missing inputs.

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 that the tool returns live inventory of ready-to-flip teens and upcoming groups by ready date, along with ordering terms. However, it relies on jargon like 'flip' and 'teens' without defining them, which slightly reduces clarity for agents without domain context.

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 does not provide any guidance on when to use this tool versus the many sibling tools (e.g., get_inventory, get_availability, list_strains). It lacks explicit conditions or alternatives, leaving the agent to infer the appropriate context from the name alone.

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