batch_update_attribute_terms

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

The annotations already declare destructiveHint=true, and the description's mention of 'delete' is consistent with that. The description adds useful operational context (single request, efficiency) but does not disclose other behavioral aspects like partial success, validation rules, or whether operations can be mixed. This is acceptable given the annotation coverage, but not rich.

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 a single sentence that is front-loaded with the tool's purpose and a concise efficiency note. Every word contributes meaning, with no redundancy or filler.

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 is adequate for a batch operation but leaves some gaps: it does not clarify whether the create, update, and delete operations can be combined in one call, nor does it mention what happens if some operations fail. With no output schema, a bit more detail about expected behavior would improve completeness. However, the required parameter is visible in the schema, and the core function is clear.

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?

The schema description coverage is 100%, and the description does not add additional meaning about the parameters beyond what is already in the schema. The baseline of 3 is appropriate since the schema carries the full burden, and the description does not elaborate on parameter use or relationships.

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's function: 'Batch create, update, or delete attribute terms in a single request.' It uses a specific verb and resource, and distinguishes itself from sibling tools like create_attribute_term and delete_attribute_term by emphasizing the batch capability.

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 usage context by stating it is 'More efficient than individual create/delete calls for multiple terms,' which implies when to use this batch tool over single-operation alternatives. It does not explicitly say when not to use it, but the guidance is clear enough for an agent to infer the appropriate scenario.

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