pipedrive_organizations_delete

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

With no annotations, the description carries the full burden. It discloses the need for confirmation and the availability of dry_run, but does not mention the irreversibility of the deletion, potential cascading effects, or authorization requirements.

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 extremely concise with two short sentences and one fragment. It front-loads the main action and has no extraneous information.

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 no output schema, the description should explain return values or success indicators, which it omits. It also does not cover error scenarios or the purpose of the 'reason' parameter. It is adequate but not comprehensive for a deletion tool.

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 coverage is 50% (org_id and confirm have descriptions; dry_run and reason do not). The description adds meaning for confirm (must be exactly 'DELETE') and highlights dry_run support, but does not explain reason or provide additional context for org_id 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 'Delete an organization', using a specific verb and resource. It distinguishes from sibling tools like create, get, update, and merge, which are all different operations.

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 mentions the confirm requirement and dry_run support but does not provide explicit guidance on when to use this tool versus alternatives, such as updating an organization to deactivate it or using soft delete if available.

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