session_list

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

The description includes a '[READ]' prefix, explicitly indicating this is a safe, read-only operation. It also discloses that it returns recent sessions and lists the output fields. Since there are no annotations to convey safety, this is valuable. However, it does not mention potential caveats like pagination, ordering, or limits, which would be useful but not critical for a simple list operation.

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 extremely concise, with no redundant words. It front-loads the core purpose in the first line and then provides the parameter details in a clear, structured format. Every sentence earns its place.

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 tool's simplicity (one optional parameter, no output schema, no annotations), the description is largely sufficient. It states what is listed and the available fields. It stops short of mentioning whether there is a limit on the number of sessions or any ordering, but these are not essential for a basic list operation.

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 description fully explains the only parameter: 'target: Veeam target name from config; omit to use the default.' This adds meaning beyond the bare schema, which only defines type (string/null) and default. It clarifies the source of the value and the behavior when omitted, which is essential for correct usage.

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: 'List recent sessions' with specific fields (id, name, type, state, result). This verb+resource combination is unambiguous and distinguishes it from sibling tools like session_get (retrieves a single session) or session_log (retrieves logs).

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 like session_get or session_log. It neither mentions exclusions, prerequisites, nor scenarios where this tool is preferred. The reader must infer usage solely from the tool name and the generic 'List' action.

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