vibe_compress

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

No annotations exist, so the description must disclose behavioral traits. It mentions token reduction (a performance trait) but omits side effects, state changes, idempotency, or any caveats about compression. This is insufficient for safe tool selection.

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?

The description is extremely concise (one sentence), but this sacrifices necessary detail. It could include parameter intent, output hints, or usage notes without becoming verbose.

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?

Given 20 sibling tools and no annotations or param docs, the description is too minimal. It doesn't explain return values (despite an output schema), constraints, or how this tool fits into a workflow. The user is left with significant ambiguity.

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?

The schema has two required parameters ('ctx' and 'data') with no descriptions. Schema description coverage is 0%, and the description adds no semantics about what each parameter expects or how to use them. This leaves users guessing.

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?

The description clearly states the action ('Compress JSON to TOON format') and a key benefit ('30-60% token reduction'). It distinguishes itself from sibling 'vibe_' tools by focusing on compression, though it doesn't explain what TOON format is.

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?

No guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, suitability, or exclusions. Users must infer from the name and context.

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