engram_compress

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

With no annotations, the description bears the full behavioral burden and discloses almost nothing: it never says whether compression is lossy or reversible, whether ES output is accepted by other tools (decompress, add_memory, etc.), or what confidence/is_code do to the result.

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, which is structurally clean. But at this length the brevity reflects under-specification rather than disciplined conciseness, so it only earns a middling score.

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 three-parameter transformation tool with no annotations, no output schema, and no parameter documentation, the description is far too thin. An agent cannot know what the compressed output looks like or whether the optional parameters matter.

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 0%, so the description must compensate and adds nothing. The 'text' input is inferable from the name, but 'is_code' and 'confidence' (integer 1-5) are completely unexplained — their effect on the compression output is unguessable.

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 output artifact (Engram Shorthand). However, 'Engram Shorthand (ES)' is jargon that is never defined, and the description doesn't differentiate this from the sibling engram_decompress beyond the obvious inverse relationship.

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?

There is no guidance on when to compress versus storing text directly, no mention of the paired engram_decompress tool, and no stated preconditions. The agent must infer all usage context.

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