pipedrive_files_list

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

No annotations are provided, so the description carries full burden. It only says 'List files', implying a read-only operation but omits details like pagination (cursor, limit), sorting, and potential rate limits. Minimal disclosure of behavior.

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 very short (6 words). While concise, it lacks structure and fails to cover essential information. It is minimally acceptable but not well-organized.

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 9 parameters, no annotations, and no output schema, the description is severely incomplete. It does not explain pagination, sorting, entity scoping details, or return format. The agent cannot effectively use this tool without additional documentation.

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%, and the description barely compensates. It mentions 'optionally scoped to an entity' but does not explain any of the 9 parameters individually (deal_id, person_id, cursor, etc.). The agent gains almost no insight 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 clearly states 'List files', which is a specific verb and resource. It adds the notion of optional entity scoping. However, it does not explicitly differentiate from sibling tools like pipedrive_files_get, but the list vs. get distinction is clear from context.

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?

No guidance on when to use this tool versus alternatives (e.g., pipedrive_files_get for specific files). The description provides no context on when scoping is appropriate or when to use other list tools.

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