Bulk Update Hazards

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. Description adds 'returns the modified object on success,' but misnames the entity (Incidents vs Hazards). No mention of required permissions, effect on other fields, or rate limits.

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?

Four sentences, but redundant (e.g., 'Update multiple Hazards' and 'Updates the specified Incidents'). Repeats required parameter from schema. Could be trimmed.

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?

Lacks explanation of bulk behavior (array of ids), no details on response structure. Confusion between Hazards and Incidents weakens completeness. No output schema to compensate.

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 100%, so parameters are documented. The description says 'only the supplied fields are changed,' which is implied by PATCH semantics, adding minimal value. No additional format or constraints explained.

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 it updates multiple Hazards, but then refers to 'Incidents' (likely a copy-paste error). This inconsistency confuses the tool's purpose. It does not clearly distinguish from siblings like bulk_update_harm_sources or bulk_update_incident_action_types.

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?

Merely says 'Use this to update an existing Incidents' without specifying when to choose this over alternative bulk update tools. No exclusions or context for when not to use it.

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