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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds essentially nothing beyond that — it notes the workspace is 'authenticated' but does not disclose pagination behavior, default result ordering, default limit, or that all filters are optional and combinable.

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?

A single front-loaded sentence with zero filler, which is appropriate for a simple list tool. It is efficient, though it is arguably too terse given the 7 parameters it silently supports.

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?

With no output schema, the description should at least sketch the returned shape or pagination contract, especially since a starting_after cursor implies paged results. An agent can call it correctly from the schema alone, but the description leaves the response model entirely unstated.

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% across all 7 optional parameters, so the schema fully documents filters, cursor, and limit on its own. The description adds no syntax, default values, or interaction rules (e.g. how q relates to format/origin), so baseline 3 applies.

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?

States a specific verb ('List') and resource ('files') scoped to the authenticated ProteinIQ workspace, which is clear on its own. However, it does nothing to distinguish itself from sibling read tools like get_file, read_file, or read_job_file, so the agent gets no help disambiguating list-vs-fetch semantics.

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?

There is no guidance on when to choose this tool over siblings such as get_file or read_file, nor any mention of how the optional filters should be combined. The description is purely a restatement of what the tool returns.

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