memory_hierarchy

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

Only the compact parameter's effect is described. No mention of read-only behavior, auth requirements, or how filter parameters influence the hierarchy. With no annotations, description carries full burden but fails.

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?

Very short but omits critical info. Not concise in a helpful sense; it's under-specified. Lacks structured breakdown of parameters or behavior beyond compact.

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?

With 9 parameters, no schema descriptions, only one parameter explained, and no output schema details (though exists), the description is severely incomplete for a complex hierarchical retrieval tool.

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%, yet the description only explains compact parameter. Eight other parameters (query, metadata_filters, etc.) are left unexplained, forcing agents to rely on names alone.

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?

Description clearly states the tool returns memories organized hierarchically from metadata, distinguishing it from flat-list or search tools. However, it doesn't elaborate on the hierarchy structure.

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 explicit guidance on when to use this tool versus alternatives like memory_list or memory_hybrid_search. The description only implies hierarchy use case.

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