list_windows

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says only that it lists windows and does not state that the operation is read-only, whether it requires permissions, pagination behavior, or any other context beyond the basic purpose.

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 filler or repetition. While it is very terse, its shortness reflects missing content rather than poor conciseness or structure.

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?

Although an output schema exists and need not be described, the tool has two required parameters with no schema descriptions and no annotations. The description does not explain alias/session usage or distinguish this tool from many related tmux siblings, leaving the agent with significant gaps for correct selection and invocation.

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% for two required parameters. The description indirectly references the session parameter ('di una sessione') but says nothing about the alias parameter, its meaning, or expected format, so it fails to compensate for the undocumented 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 states a specific verb ('Elenca') and resource ('finestre') scoped to a session, making it distinguishable from sibling list tools like list_sessions or list_hosts. It does not, however, name the alternative window-specific tools (new_window, kill_window) or otherwise differentiate from them.

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?

There is no guidance on when to use this tool versus alternatives such as list_sessions or session_details, nor any prerequisites or exclusions. Usage is only implied by the tool name and the phrase 'di una sessione'.

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