Bulk Update Contributing Behaviors

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

The description discloses that it performs a partial update ('only the supplied fields are changed') and returns the modified object, adding value beyond annotations which indicate non-readonly and non-destructive behavior.

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 relatively concise but contains redundancy (refers to Incidents instead of Contributing Behaviors) and includes endpoint/API details that may be extraneous.

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?

The description provides the endpoint and return behavior but lacks details on error handling, success/failure partial behavior, or response structure. Given no output schema, this leaves gaps.

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% with clear parameter descriptions. The description adds partial update context but does not elaborate on parameter constraints or syntax 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 it updates multiple Contributing Behaviors, distinguishing it from single update tools. However, it incorrectly refers to 'Incidents' in places, causing confusion.

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 implies this tool is for bulk updates but does not explicitly state when to use it over alternatives like 'update_contributing_behavior' (single update). No when-not-to-use guidance.

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