ecommerce_context_compressor

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states that a DOM is compressed to micro-JSON but says nothing about whether the operation is read-only, what the micro-JSON structure looks like, how invalid input is handled, or whether any external calls are made.

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 with no filler, and the core action is front-loaded. However, it is so terse that it omits context that would help an agent use it correctly, so it is efficient rather than fully informative.

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?

The input schema is simple, but there is no output schema and no annotations, so the description should explain the returned 'micro-JSON' shape and the intended use case. It does neither, leaving an agent uncertain about what the result contains and when this tool should be preferred.

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, but it adds only the word 'DOM' and the notion of compression. The schema already exposes domString as a string, so the description provides no additional meaning about expected format, size limits, or how the DOM string should be serialized.

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 names a specific verb ('Compress'), a clear input ('DOM'), and an output format ('micro-JSON'), so an agent can tell what operation is intended. It does not explicitly differentiate this from sibling tools like ecommerce_visual_dom_analysis, and 'micro-JSON' is left undefined, so it falls short of a 5.

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 use this tool versus any alternative, no mention of context reduction use cases, and no indication of prerequisites. The description is purely a transformation statement and leaves any usage decision to inference.

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