bulk_update_entities

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the write nature is known, but the description adds nothing beyond that: it does not explain that a `confirm: true` acknowledgement is required, whether per-entity failures abort the whole batch, or whether `fields` merges into or replaces existing values. Note the schema's `confirm` text calls this a 'destructive/bulk operation', which conflicts with destructiveHint=false – a tension the description does nothing to resolve.

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 the verb and target resources first and the modified attributes after the colon; there is no filler. It is slightly cramped but appropriately sized for the tool.

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 six parameters (including nested objects), two required fields, and no output schema, the description is too thin: it omits the confirmation requirement, batching limits, failure semantics, and which entity types/ids go where. An agent would have to infer the safe invocation pattern entirely from the schema.

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 83%, so the schema already carries most parameter meaning. The description's enumeration of 'fields, comment and links' loosely maps to three of the six parameters but adds no syntax, format, or constraint detail beyond what the schema provides – the baseline 3 for high coverage.

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 (bulk update) and the three resource types it operates on (projects, portfolios, goals), plus what is changed (fields, comment, links). This implicitly separates it from siblings like bulk_update_issues and bulk_move_issues, but it never names an alternative tool explicitly.

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 or when-not-to-use guidance, no mention of prerequisites, and nothing about the required `confirm` flag or any cap on how many entities can be updated in one call. 'At once' only hints at the efficiency motivation without stating conditions.

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