list_expected

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

No annotations provided, so description carries full behavioral disclosure burden. It explains return format (raw API response with visit ID, company, time window) and mentions pagination/sorting defaults. Could explicitly state read-only nature, but implied as list operation.

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?

Well-structured with front-loaded purpose, then usage guidelines, then parameter documentation in a clean Args block. Every sentence adds value, 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 5 parameters and no output schema, the description covers purpose, usage, parameter semantics, return format, and prerequisite call. Sufficient for an agent to correctly select and invoke the tool.

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% (no parameter descriptions in schema), but the description compensates with detailed explanations for each parameter: apartment_id source, page/page_size defaults, sort_order enum, fields dot-notation filtering.

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 it lists pre-approved deliveries pending arrival, with specific verb 'list' and resource 'expected deliveries'. It distinguishes from sibling tool 'list_visits' which is for historical gate activity.

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?

Provides explicit when-to-use (user query examples like 'what have I pre-approved?') and when-not-to-use (historical: use list_visits). Also specifies prerequisite to call get_user_multiprofile_info to obtain apartment_id.

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