pipedrive_files_list

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing. Pagination, sort behavior, permissions, and result shape are all unmentioned; only the schema's cursor/limit params hint at paging. This is a significant gap for a nine-parameter listing tool.

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 short sentence is front-loaded and waste-free, but for a nine-parameter tool with no annotations and no output schema it is arguably too terse rather than genuinely concise. It is appropriately sized only in the loosest sense.

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 annotations and no output schema, the description should convey more about return behavior and filtering semantics, but it does not. The high schema coverage mitigates the parameter gap, yet the absence of any behavioral or return context leaves the definition incomplete for a listing endpoint.

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 89%, so the schema already documents each filter (org_id, deal_id, person_id, etc.) and the pagination params. The description adds only the abstract notion of entity scoping, which is marginal value beyond what the schema states. Baseline 3 applies when the schema does the heavy lifting.

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 and resource ('List files') and adds a scoping hint ('optionally scoped to an entity'), which distinguishes it from the singular pipedrive_files_get. However, it does not name or contrast the sibling, and the notion of 'entity' is left ambiguous given nine possible entity filters.

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 phrase 'optionally scoped to an entity' implies the tool can be used broadly or filtered, but there is no explicit when-to-use guidance, no mention of the alternative (files_get for a single file), and no exclusions. The agent must infer routing from the schema alone.

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