Compress a file exactly

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

Annotations already declare the mutation/idempotency/open-world profile, and the description adds real context beyond them: bit-exact lossless semantics, the default output naming convention, and a post-run exact-restore hash check. It doesn't mention performance, size limits, or failure modes, keeping it below a 5.

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?

Three tight sentences, front-loaded with purpose, then inputs, then return summary. Every sentence earns its place with no redundancy against the schema or annotations.

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 an output schema existing, the description briefly summarizes the return payload (output path, bytes in/out, ratio, restore check), and covers inputs, semantics, and the decompress counterpart. Nothing needed to invoke correctly 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?

With schema description coverage at 0%, the description carries the parameter burden and does: it defines path as a local file path and out_path as optional defaulting to path + '.sing'. Both parameters are meaningfully documented, though no format or path-type detail is given.

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 (compress a file) with the distinguishing qualifier 'exactly (lossless, bit-exact restore)'. Names the inverse sibling singularis_decompress, so an agent can immediately tell it apart from the many other singularis_* compute tools.

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 concrete use cases (archives, datasets, logs, model checkpoints) and the selecting condition 'anything that must come back identical', plus routes to singularis_decompress for the inverse. It stops short of explicit when-not-to-use or non-lossless alternatives, so not a full 5.

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