Check custom-order availability

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

With no annotations, the description carries the full burden. It clearly indicates a read-only reporting operation by specifying the exact outputs: whether lead time is met, days out, and earliest available date. It does not cover edge cases or validation behavior, but the core behavior is well disclosed.

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 well-structured sentence that front-loads the input ('Given a requested YYYY-MM-DD date') and lists the three concrete outputs. Every word earns its place with no fluff.

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 lack of annotations and output schema, the description explains the main return values but omits parameter semantics for orderType and provides no usage guidance versus sibling tools. It is minimally viable for a simple availability check but has clear gaps.

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 0%, and the description only clarifies the 'date' parameter format (YYYY-MM-DD). The optional 'orderType' parameter is completely undocumented, leaving the agent without guidance on its values, purpose, or effect on the availability check.

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 reports whether a date meets custom-order lead time, how many days out, and the earliest available date. This specific verb+resource distinguishes it from sibling tools like submit_order_inquiry, get_menu, and get_business_profile.

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 gives clear context: use when you have a requested date and need availability/lead-time information. It does not explicitly name alternatives or exclusions, but the purpose is unambiguous, so it narrowly misses a 5.

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