Bulk Update Materials

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

Annotations indicate this is a write (readOnlyHint: false) and non-destructive (destructiveHint: false) operation. The description adds that only supplied fields are changed and the modified object is returned, which is useful. However, it does not disclose potential partial failure, permission requirements, or other side effects beyond the annotation's safety profile.

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 with a few sentences, but contains a grammatical error ('an existing Field Productivity records') and redundant listing of required parameters already in the schema. The API path and tool category are helpful but add length. It could be more streamlined without losing key 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 the lack of output schema and vague array item type in the input schema ('{}'), the description does not adequately compensate. It does not explain what constitutes a 'Material' or the expected fields in the array. The return value description ('modified object') is vague. The API path and category provide some context, but the tool is not fully self-contained for an agent to use correctly.

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 the parameters have adequate descriptions. The description repeats the required parameters but adds no new meaning. It does not explain the structure of the 'time_and_material_materials' array (e.g., what fields each Material object should contain), which the schema only defines as '{}' (empty). Thus, the description adds no extra value 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 the tool performs a bulk update of Material entries in one request, with partial updates. It uses the verb 'bulk update' and specifies the resource. However, it ambiguously refers to 'Field Productivity records' interchangeably, which may cause confusion. It does not explicitly differentiate from sibling tools like 'update_material' for single updates, but the 'bulk' prefix implies that.

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 provides limited guidance on when to use this tool. It says 'Use this to update existing Field Productivity records' but does not mention when not to use it, such as for single updates (use 'update_material') or for creating/deleting materials. No alternatives are mentioned, and the context of bulk operations could be better clarified.

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