conduyt_bulk_edit_deals

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

No annotations are provided, so the description carries the behavioral-disclosure burden. It usefully states that this is a bulk mutation and requires deals:edit, but it does not explain overwrite semantics, partial-failure behavior, reversibility, or what the response contains.

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?

Three short sentences front-load the core behavior, then immediately provide the sibling alternative and permission requirement. Every sentence contributes directly to correct tool selection or invocation.

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 two-parameter bulk mutation tool with a fully described schema, the description supplies the key usage distinction, an example, and the required permission. It is nearly complete, but without annotations or an output schema it still leaves return behavior and partial-failure handling unmentioned.

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 both ids and updates are already documented in the input schema, including an example for updates. The description reinforces that one updates object is applied to all ids, but adds little syntax or constraint detail 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 states a specific verb and resource: bulk-edit deals by applying the same field changes to many deals at once. It also distinguishes this tool from the sibling conduyt_bulk_update_deals, which is for different values per deal, so an agent can identify the correct bulk operation without opening the schemas.

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?

It explicitly says when to use this tool: when the SAME field changes apply to many deals, e.g. reassigning a set of deals to one user. It also names the alternative for different per-deal values and states the required permission, giving clear selection guidance.

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