incomplete_uploads_ls

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

readOnlyHint=true already declares the safety profile, and the description adds real behavioral context beyond it: the truncation-aware envelope, the exact return keys, the null-initiated-time edge case, and the re-run-on-truncation remedy. With no output schema present, this return-shape disclosure is valuable rather than redundant.

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?

Front-loads the [READ] tag and purpose, then the return envelope, then a compact Args block. Every line earns its place with no filler, and the pagination remedy is placed where it is needed.

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 4-param, read-only listing tool with no output schema, the description covers purpose, return format, edge cases, and all parameters. Combined with the readOnlyHint annotation, an agent has everything required to call it correctly.

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 0%, so the description carries the full parameter burden and does so completely: it explains bucket_name (pointing to bucket_ls as its source), prefix semantics ('empty for the whole bucket'), limit with its default, and target with the 'omit for the default' rule. This adds meaning well beyond the bare schema titles.

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+resource ('in-flight/abandoned multipart uploads') with a [READ] scope tag, so the agent knows it lists rather than deletes. It does not, however, differentiate from the sibling remove_incomplete_uploads (its write counterpart) or object_ls, so sibling disambiguation is left to inference.

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 gives one actionable operational rule ('When truncated is true, re-run with a higher limit'), which is genuinely useful. But it offers no when-to-use/when-not guidance relative to alternatives like remove_incomplete_uploads or object_ls, so the usage context is only implied.

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