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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond the name — it does not disclose whether the response is paginated, whether it includes nested folders, or how a 'flat list of all folders' relates to the folder tree.

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 short sentences, front-loaded with the purpose. The second sentence is a raw endpoint restatement that adds little beyond the path, but it is not wasteful enough to penalize below 4.

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 tool is simple (no params, no output schema, safety covered by annotations), but the description omits the one thing that matters here: how the returned 'all folders' set relates to the sibling folder_root and folder_id tools, and whether the result is flat or hierarchical.

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 takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies for a parameterless listing endpoint.

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?

States a clear verb+resource combination ('Get all LLM session folders'), which an agent can act on. However, it does not distinguish itself from two near-identical siblings, get_strategy_llm_session_folder_root and get_strategy_llm_session_folder_id, leaving ambiguity about whether this returns a flat list, the root, or a tree.

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 call this versus the sibling folder tools (folder_root, folder_id). The 'all' phrasing implies a listing scope, but no alternatives or conditions are named.

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