session_files

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only states that the tool lists files with optional cursor-based pagination; it does not disclose outputs, error behavior, path handling, recursion, permissions, or the meaning of 'bounded.'

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 one concise, front-loaded sentence that delivers the core purpose and a key optional behavior without unnecessary words. It earns its place and is easy to parse.

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 no output schema, no annotations, and four parameters, the description is under-specified. It does not explain what the returned file listing contains, how path filtering works, how cursor/page_size interact, or what a bounded cursor page means in practice.

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 must compensate for the four parameters. It only hints at cursor/page_size via 'bounded cursor page' and provides no explanation of session_id, path, or pagination semantics beyond that.

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 action ('List') and the resource ('workspace files'), and adds a distinguishing pagination detail ('optionally using a bounded cursor page'). This separates it from related tools like session_read_file and session_write_file.

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 intended use is implied by the phrase 'List workspace files,' but there is no explicit guidance on when to choose this tool over siblings like session_list, session_artifacts, or session_read_file. No when-not-to-use conditions or alternative recommendations are provided.

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