rag_snapshots_list

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

There are no annotations, so the description carries the full burden of explaining behavioral traits, but it only says 'List'. It does not clarify what 'effective' means, how session_id affects results, whether layers are returned in a flat or nested structure, or whether any side effects occur.

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 a single front-loaded sentence with no wasted words. It conveys the core operation and object clearly enough for quick parsing.

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 presence of an output schema and a single optional parameter makes this minimally viable for invoking the tool. However, the undefined 'effective' qualifier, missing parameter guidance, and absence of usage context leave notable gaps for an agent deciding when and how to call it.

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% and the description does not mention session_id at all. The parameter name and title are somewhat self-explanatory, but the description adds no meaning about how session_id selects or scopes the snapshots.

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 identifies a specific operation ('List') and a specific resource ('effective RAG snapshots and their layers'), which is enough to distinguish it from creation-oriented RAG tools. However, it does not explicitly differentiate itself from other RAG list/query tools, and 'effective' is left unexplained.

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 no guidance on when to use this tool versus alternatives such as rag_snapshot_create, rag_sources_list, or rag_query. It states only what the tool does, leaving the agent to infer the appropriate context.

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