list_workspace_files

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

readOnlyHint=true already conveys that this is a safe read operation; the description adds useful scoping context ('vendor has shared', file type categories) but does not disclose pagination, sorting, or the shape of the returned file list. Since there is no output schema, those details are not available elsewhere.

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 sentence with no filler; the parenthetical examples (contracts, invoices, brochures, proposals) quickly communicate the tool's domain. The main purpose is front-loaded and every element earns its place.

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 two optional parameters, zero required parameters, and a fully documented schema, the description is sufficiently complete for an agent to invoke it correctly. It could be stronger by noting how it differs from get_workspace_file, but that is a minor gap for such a simple operation.

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 100%, so both origin and file_type are already documented structurally. The description only paraphrases the file_type filter ('Optionally filter by file_type') without adding new meaning beyond the 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 and resource ('List all files a vendor has shared with you') and gives concrete file type examples arena. It reads as a clear list-all operation, but it does not explicitly distinguish itself from the sibling get_workspace_file or clarify when that singular tool should be used instead.

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 no guidance about when to choose this tool over alternatives like get_workspace_file or list_attachments. The 'Optionally filter by file_type' clause is parameter usage rather than usage selection guidance, leaving the agent to infer when this tool is appropriate.

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