list_trees_by_session

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

With no annotations, the description carries the burden of indicating the tool is a read-only listing operation. The verb 'List' implies a non-destructive read, and 'all trees associated with a session ID' states the core behavior. However, it does not disclose whether any side effects, auth requirements, ordering, or pagination happen. This is a basic but acceptable level of transparency.

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?

One sentence with no redundant phrasing. The verb, resource, filter, and purpose are all front-loaded and clear.

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 simple list tool with one parameter and no output schema, this description is nearly sufficient. It explains what the tool does and why it is used, though it stops short of describing the return format or behavior when no trees match the session. This is a minor gap for straightforward call/invocation decisions.

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%, and the sessionId parameter is already described as the filter. The description adds only the phrase 'specific session ID,' which does not materially improve semantic understanding beyond the schema.

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 uses a specific verb ('List') and resource ('all trees') and clearly scopes it to a specific session ID. It distinguishes this tool from siblings like list_trees and list_trees_by_strategy by the session-based filter.

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 phrase 'for context maintenance' implies a use case, but the description does not explicitly say when to use this tool over alternatives like list_trees_by_strategy or get_session_context. No exclusions or alternative routing are provided.

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