pipedrive_files_upload

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

With no annotations, the description carries the full behavioral burden, and it discloses very little. It does not state permission requirements, file-size or base64 payload limits, what happens if multiple or zero entity IDs are supplied, or whether the attachment is reversible. 'Upload' implies mutation but nothing else is clarified.

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 well-sized. It is efficient, though the brevity comes at the cost of the missing attach-target constraint rather than being purely tight writing.

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 nine-parameter mutation tool with no annotations and no output schema, the description is thin. It never explains the mutually-exclusive entity attach parameters, payload constraints, or the shape of the response, leaving gaps the structured fields do not cover.

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 all nine parameters (org_id, deal_id, lead_id, person_id, product_id, activity_id, file_name, mime_type, content_base64) are already documented in the schema. The description adds no syntax, format, or selection guidance beyond that, so the 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?

The description states a specific verb ('Upload') and resource ('base64-encoded file') plus the effect ('attach to an entity'), which is more than a restatement of the name. It does not, however, distinguish this tool from the sibling file tools (pipedrive_files_get, pipedrive_files_list) beyond what the name already implies.

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 when-to-use guidance, no mention of alternatives, and no indication of the key operational constraint: that the caller must pick exactly one of the eight entity parameters to attach to. The agent is left to infer the attach-target rule entirely.

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