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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is established. The description adds useful behavioral context beyond annotations by specifying how the path parameter changes the output granularity (whole layout vs. scope-specific files vs. one file per clip/link).

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 three sentences, front-loaded with the core action, and every sentence contributes concrete path-scoping information. The parenthetical shorthand is compact and effective, with no redundant or filler content.

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 read-only list tool with a single optional parameter and an output schema, the description is complete. It explains all documented path patterns and leaves return-value details to the output schema, so nothing essential for invoking the tool correctly is missing.

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%, so the description carries the full burden of explaining the 'path' parameter. It does so thoroughly with three illustrative patterns, including the default empty-string behavior, which makes the parameter semantics clear and actionable.

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 opens with 'List workspace files,' a specific verb and resource, and then details the exact path patterns that control the listing scope. This clearly distinguishes it from sibling tools like ws_read (reading content) and ws_grep (searching).

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 clear context on how to use the tool through concrete path examples ('' for whole layout, 'job/<job_id>', 'project/<project_id>', 'job/<job_id>/transcript'). It does not explicitly name alternatives or say when not to use this tool, but the operation is clear enough that the intended usage is unambiguous.

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