capture_list_files

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

Annotations already establish read-only, idempotent, and non-destructive behavior. Description adds a meaningful behavioral detail: in ring buffer mode, multiple files may exist, which helps set expectations about the result set. No contradiction with annotations.

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 concise sentence that front-loads the primary purpose and adds a relevant qualifying note. No redundant or obscure wording.

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 low complexity (one parameter), the presence of annotations, and an output schema (not shown but indicated), the description adequately covers the core behavior and an important edge case. It does not describe return values, but the output schema covers that. Slight room to mention common usage context (e.g., after capture_start), but not necessary.

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?

Single parameter capture_session_id is self-explanatory in name and type. Schema coverage is 0%, but the description does not elaborate on the parameter; however, the parameter is simple enough that little extra is needed. The description adds no additional semantic nuance.

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?

Clear verb 'list' with specific resource 'files produced by a capture session'. Differentiates from sibling tools like capture_list_sessions (lists sessions) and capture_list_interfaces (lists interfaces). The scope is well-defined.

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?

Implies use case (listing files for a capture session) and adds context about ring buffer mode, but does not explicitly state when to use this tool versus alternatives or when not to use it. No comparison with capture_list_sessions or file listing tools.

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