Find the largest files (server-side scan)

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

Annotations cover only readOnly/openWorld, but the description discloses operational traits the agent could not otherwise know: a single shared task slot that clears stale tasks, interference between concurrent scans, and that `complete` may be false with partial results on timeout. It also quantifies the server-side speed advantage over client-side walking.

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 purpose and use case, then layers caveats and alternatives. Every sentence carries distinct information — performance rationale, concurrency warning, completeness check — with no restatement of the schema.

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?

Despite a return shape being restated (redundant given the output schema exists), the definition covers everything an agent needs: purpose, alternatives, concurrency hazard, partial-result signal, and safety profile. Nothing material is missing.

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 `top`, `paths`, and `min_size_mib` are already documented in the schema; the description adds only the ordering guarantee ('biggest first') which is not a parameter property. Baseline 3 is appropriate when the schema carries parameter meaning.

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 and resource with ordering semantics: 'List the largest files under the given directories, biggest first.' It also explicitly differentiates itself from zspace_du and zspace_usage, so an agent can route without opening any schema.

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?

Gives a concrete use case ('find cleanup candidates') and names the two alternatives with the condition that selects each: zspace_du for a directory's total size, zspace_usage for pool-level accounting. This is explicit when-to-use and when-not-to-use guidance.

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