logistics_audit_telemetry

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

With no annotations, the description carries the full burden. It discloses processing behavior beyond schema: verifying GPS geofence arrival within a default 500m tolerance, calculating a deterministic Merkle Root, and identifying SLA threshold breaches. However, it omits permissions, side effects, and whether the operation is read-only, leaving meaningful behavioral gaps.

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 single sentence is front-loaded with 'Audits cold-chain...' and every clause contributes specific scope. It is dense but contains no filler, though splitting it into shorter sentences would improve readability slightly.

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?

For a complex tool with 5 parameters, no annotations, and no output schema, the description covers the core audit behavior and implies outputs (Merkle Root, SLA breaches). It lacks explicit return format details, but gives enough for an agent to understand invocation and purpose.

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 100%, so the baseline is 3. The description adds value by naming sensor log contents (humidity, shock, E-Seal tamper status) that the schema example omits, and by confirming the default 500m geofence tolerance that maps to maxGeofenceMeters. This exceeds the schema's own descriptions.

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?

States a specific verb ('Audits') and resource ('cold-chain and transit environmental sensor logs') and enumerates key operations: temperature/humidity/shock/E-Seal audit, GPS geofence verification, Merkle Root calculation, and SLA breach identification. This clearly distinguishes it from logistics_verify_ebl and logistics_issue_pod_attestation, which handle different logistics artifacts.

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 state when to use this tool versus alternatives, nor does it include prerequisites or exclusions. Usage is only implied by the tool's purpose, matching the calibration MID case where lack of explicit when-to-use guidance scored 2.

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