singularis_compress

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

With no annotations, the description carries the full burden and does well: it states the lossless guarantee, the default output naming, and the existence of an exact-restore verification (hash of trial restore equals original). It omits overwrite behavior, permission/auth needs, and file size or rate limits.

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 core purpose and usage, then parameter details, then the sibling routing. Efficient overall, though the return-value sentence is partly redundant given the tool has an output 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?

For a simple two-parameter tool with an output schema and no annotations, the description covers purpose, when to use, parameters, and the verification guarantee. Missing edge-case behavior (overwrite handling, failure modes) keeps it from being fully complete.

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 must compensate, and it does: path is described as a local file path and out_path is documented with its default (path + '.sing'). It does not cover path format constraints such as relative vs. absolute paths, leaving a small gap.

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 (Compress) and resource (a file) with a defining qualifier (exactly, lossless, bit-exact restore) that distinguishes it from sibling singularis_decompress. An agent knows immediately what the tool does.

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?

Explicitly lists use cases (archives, datasets, logs, model checkpoints, anything that must come back identical) and routes to singularis_decompress for the inverse operation. It implies when-not (anything not requiring bit-exact restore) but never states it outright.

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