get_delivery_schedule

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

No annotations are provided, so the description carries full burden. It states it's a read operation ('View'), which is clear, but lacks details on behavioral traits like permissions needed, rate limits, pagination, or error handling. The description doesn't contradict annotations, but it's minimal for a tool with no annotation support.

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, efficient sentence that front-loads the key action ('View all upcoming deliveries') and adds necessary details (what's included). Every word earns its place with no waste or redundancy.

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 has no parameters, no annotations, and no output schema, the description is adequate as a basic read operation but lacks completeness. It doesn't explain the return format, potential errors, or how it integrates with sibling tools like 'modify_delivery', leaving gaps for an AI agent.

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 tool has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description appropriately focuses on the tool's function without redundant parameter info, meeting the baseline for zero-param tools.

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's purpose with a specific verb ('View') and resource ('upcoming deliveries'), including what information is returned (dates, selected meals, delivery status). It distinguishes from siblings like 'get_past_orders' (past vs upcoming) and 'modify_delivery' (read vs write), though not explicitly named.

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 for viewing upcoming deliveries, suggesting when to use it (for upcoming info) versus alternatives like 'get_past_orders' (for past info). However, it lacks explicit guidance on when not to use it or direct comparisons to siblings, leaving some context to inference.

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