Get Eden Session Storage

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

Annotations already declare readOnlyHint and idempotentHint, but the description adds value by explicitly stating 'never deletes files' and detailing the classification categories. This reinforces the safety profile and gives richer behavioral context without contradicting the annotations.

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 two sentences, front-loaded with the primary purpose and a clear safety note. Every sentence earns its place with no repetition of the title or schema.

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 the low complexity (no parameters) and presence of an output schema, the description fully covers what the tool does and its safety behavior. It is complete for an agent to select and invoke the tool appropriately.

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 tool has zero parameters, and the schema covers all (none) with 100% coverage, so the baseline is 4. The description adds no parameter-specific details, but none are needed since there are no inputs to explain.

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 tool's function: 'Inventory managed-session disk usage and classify active, reclaimable, protected, unconfirmed, and legacy directories.' This specifies a concrete verb and resource, and distinguishes it from cleanup-oriented siblings like eden_cleanup_sessions.

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?

The description provides clear context by stating 'This tool never deletes files,' which implies it should be used for inspection rather than cleanup. It does not explicitly name alternative tools for deletion, so it stops short of full when/when-not guidance, but the non-destructive implication is strong.

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