gc_hindsight

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

With no annotations provided, the description carries full disclosure burden, but it discloses almost nothing: no mention of backend availability, auth requirements, latency, side effects of 'retain', or what happens when the backend is unreachable. It does note 'Foresight expected to succeed it', which hints at instability, but says nothing about operational behavior or risks.

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 short (one sentence plus an action list), which is efficient, and it front-loads the proxy/backend context. But conciseness here approaches under-specification—it's a single dense sentence that crams backend substitutions without providing usable structure for an agent deciding how to invoke it.

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 tool with 4 distinct actions, 7 params (1 nested object), and no output schema, the description is severely under-specified. It doesn't explain each action's return, behavior, or param requirements, nor does it note that dedicated sibling tools exist for the same actions. Given the complexity and zero annotations, this is materially incomplete.

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 baseline is 3, but the description adds zero parameter context beyond what the schema already provides. The description doesn't clarify how parameters map to each action (e.g., which params apply per action), how actions interrelate, or format requirements. It fails to compensate for the ambiguity of 7 params affecting different actions differently.

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 calls it a 'Direct proxy to the deep-memory backend' and lists four actions, but it never states WHAT the tool actually does in user terms. It doesn't explain what 'recall', 'reflect', 'retain', or 'health' accomplish semantically. The enum in the schema partially conveys purpose but the description adds little beyond naming the backend. Notably, gc_recall and gc_recall siblings exist, so the distinct purpose is unclear.

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 proxy tool vs the dedicated sibling tools (gc_recall, gc_retain, gc_reflect) which likely cover the same actions more specifically. No context on use cases, prerequisites, or exclusions. The description gives no decision support for when this umbrella proxy is the right choice.

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