Check File Transfer Control

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

The description adds real behavioral context beyond the annotations: the call blocks/waits, and it can only proceed at a 'safe block boundary' while cancellation is pending. It does not say how long it waits, whether there is a timeout, or what happens if cancellation is never confirmed. The 'safe block boundary' phrasing is unexplained jargon.

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 front-loaded sentence with no filler; the blocking condition is attached to the core action. It is efficient, though the compressed jargon ('safe block boundary') trades clarity for brevity.

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?

An output schema exists, so return values need not be described, and the annotations cover the read-only posture. But in a family of ~35 terminal_* siblings heavily clustered around file-transfer leases and cancellation, the description gives no routing information, leaving an agent unable to select it confidently.

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 coverage is 100%, so both session_id and owner are already documented, and the description adds nothing about them. Notably it never mentions that owner is a required opaque capability, but with full schema coverage the baseline of 3 applies.

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 names a specific resource (a file-transfer lease) and a specific action ('check ... at a safe block boundary'), which goes beyond the tautological title 'Check File Transfer Control'. However, the verb 'check' is vague and the phrase gives no way to tell this apart from closely named siblings such as terminal_wait_file_transfer, terminal_report_file_transfer, or terminal_release_lease, all of which operate on the same lease.

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?

It states a condition ('while cancellation confirmation is pending') but never says when an agent should call this rather than terminal_wait_file_transfer, terminal_report_file_transfer, or terminal_resolve_file_transfer_cancel. There is no explicit when-to-use, when-not-to-use, or named alternative anywhere in the text.

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