cpu_finalize_delivery

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

With no annotations provided, the description carries the full burden. It discloses key behaviors: permissionless, on-chain (gas cost), crediting to target cell, and session requirement. It could be more explicit about error handling or if the operation is atomic, but the provided details are sufficient for understanding the core behavior.

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 highly efficient: two sentences covering purpose, prerequisites, and usage context. Every sentence adds necessary information without 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's simplicity (single parameter, no output schema), the description covers all necessary aspects: what it does, when to use it, prerequisites, and a pointer to the source of valid input. The return behavior is implicit (crediting to target cell) and adequately communicated.

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 describes the parameter 'ids' as on-chain delivery IDs. The tool description adds value by specifying that these come from 'list_my_transports' and must be for arrived deliveries, providing practical guidance beyond the schema.

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 action (finalize), resource (arrived deliveries), and effect (crediting to target cell). It also distinguishes itself by noting it is permissionless and on-chain, and references a sibling tool for finding eligible deliveries.

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 specifies when to use the tool (only after arrival time has passed), prerequisites (requires a session via cpu_authenticate), and directs users to cpu_list_my_transports to check which deliveries are ready to finalize. It also notes the permissionless and on-chain nature.

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