verify_delivery_file

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

The description describes a read-only verification operation, but the annotation readOnlyHint=false contradicts this, suggesting the tool may have side effects not mentioned. The description fails to disclose any behavioral traits beyond the annotation, such as whether it modifies files or state.

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?

A single sentence efficiently conveys the tool's core actions without redundancy. Key information is front-loaded, and every part is essential.

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?

The description explains the tool's actions but does not mention return values or output schema, which is important for a verification tool. With no output schema provided, the description should hint at whether it returns a boolean, checksum, or status. The coverage of parameters is complete, but the lack of output information is a gap.

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 description adds meaning beyond the schema by explaining that the tool verifies a non-empty regular file (tying into minimum_size_bytes) and calculates a checksum (tying into checksum_algorithm). The optional comparison of size and checksum maps to expected_size_bytes and expected_checksum. Though schema has 100% description coverage, the description enriches parameter understanding.

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: verify a delivery file, check that it's a non-empty regular file, calculate a checksum, and optionally compare against expected values. The verb 'verify' and resource 'exported delivery file' are specific, and the description distinguishes it from sibling tools that handle editing, effects, or other operations.

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 use after exporting a delivery file but does not explicitly state when to use this tool over alternatives. No exclusions or comparisons with other verification or export-related tools are provided, leaving usage context vague.

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