products_list_files

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

No annotations are provided, so the description carries full burden. It mentions file types and sorting, but does not disclose read-only nature, error handling, permission requirements, or pagination behavior (start/limit are in schema). The description is adequate but lacks depth.

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 concise with a clear structure: main purpose, file type examples, sorting info, and use-case bullet list. It front-loads the key action. A minor improvement would be merging the bullet list into a more compact statement, but it's well-organized overall.

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 4 parameters, no output schema, and no annotations, the description covers key aspects but lacks details on output structure, error cases, or implicit constraints (e.g., product existence). It is functionally complete for a list tool but leaves gaps.

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 baseline is 3. The description reiterates sorting fields (id, update_time) that are already in the schema, but adds no new parameter-level details. It does not compensate for missing enums or constraints beyond what the schema provides.

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 'List all files attached to a specific product,' which is a specific verb and resource. It lists common file types and sorting options, and the product-specific scope distinguishes it from sibling tools like 'files_list' or 'deals_list_files'.

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 explicit use cases: 'Viewing product documentation,' 'Accessing product images,' 'Managing product attachments.' It does not include negative examples or when to use alternative tools, but the guidance is clear and actionable.

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