hyperspace_cache_config

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

No annotations are provided, so the description carries the full behavioral burden for a mutation tool. It usefully states the return format ('Returns updated config as JSON result'), but says nothing about permission requirements, whether the change is persisted or reversible, or whether existing cached entries are invalidated when the policy changes.

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?

Two tight sentences with zero filler: the mutation and its scope come first, the return value second. Every clause earns its place.

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?

A three-parameter mutation tool with full schema coverage and no output schema, partially compensated by the stated JSON return. However, with no annotations and no mention of side effects or failure modes when an unsupported policy string is supplied, the definition is only minimally sufficient for safe invocation.

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 100%, so all three parameters (policy, collection, ann_threshold) are already documented in the schema. The description only restates the policy and ANN threshold fields without adding formats, valid ranges, or defaults, so baseline 3 applies.

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 gives a specific verb and resource ('Update L0 Cache configuration') and even enumerates the two settings it touches (eviction policy, ANN threshold) scoped to a collection. It is clearly differentiable from hyperspace_cache_stats and hyperspace_cache_clear by name and semantics, though it never explicitly contrasts itself with them.

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 reach for this tool versus cache_clear, cache_stats, or collection-level tuning, and no preconditions (e.g. collection must exist, cache must be enabled, whether changing policy flushes entries). The purpose sentence only implies usage; it does not route the agent.

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