analyze_on_time_delivery

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

With no annotations provided, the description carries the burden of behavioral disclosure. It does this well by revealing the matching heuristic ('closest Purchase Order due date') and the outputs computed. It does not explicitly state that the tool is read-only or describe data prerequisites, but the analytical nature and detail are sufficient for a low-risk analysis tool.

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 two focused sentences with no wasted words. The first sentence states the domain, and the second provides the methodology and outputs. It is well front-loaded and easy to scan.

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's low complexity, a single documented parameter, and no output schema, the description is largely complete: it states the analysis method, grouping, and calculated metrics. It could be more explicit about the return format, but it provides enough for an agent to invoke the tool and interpret the likely result.

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 schema already documents the only parameter, months, with its default and maximum value, so the description need not add parameter details. There is no extra semantic value about how months affects the analysis, but 100% schema coverage makes this acceptable.

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 identifies the resource (vendor on-time delivery) and explains the exact method: matching Goods Receipt POs to the closest Purchase Order due date and computing on-time%, early/late counts, and average delay days per vendor. This distinguishes it from sibling tools like analyze_vendor_lead_time or analyze_vendor_concentration, though it does not explicitly name an alternative.

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 the tool is used for assessing vendor delivery punctuality, but it gives no explicit when-to-use guidance, prerequisites, or contrast with related analysis tools. An agent must infer the appropriate context rather than being told when this tool is preferred over alternatives.

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