list_plots

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 states the scope (files under the shows root), ordering (newest first), and the fields returned for each entry. This is solid transparency for a read-only listing operation, even though failure modes and path conventions are not mentioned.

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 organized into three short, purposeful parts: the core listing behavior, the entry fields, and the practical use case. Every sentence contributes new information, and the most important detail (what the tool does) is front-loaded.

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?

An output schema exists, so the entry fields do not need to be exhaustively documented in the description. The description still covers scope, sort order, and a decision-relevant use case, making it complete enough for an agent to invoke correctly.

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 only parameter, limit, is not described in the text, and schema description coverage is 0%. The schema's property name and default value imply its meaning, but the description adds no additional explanation or usage nuance. Since the parameter is simple, the gap is moderate rather than severe.

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 opening sentence states a specific action and resource: list Lightwright XML files under the shows root, and it adds the sort order (newest first). This clearly distinguishes the tool from siblings like set_active_plot and get_active_file, which focus on selection or retrieval rather than discovery.

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 gives a concrete use case: picking a plot when multiple shows are open or when set_active_plot returns ambiguous matches. This provides clear guidance on when to call the tool, though it does not explicitly state when not to use it or name alternative list-producing tools.

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