zero_update_element

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

With no annotations, the description carries full behavioral disclosure. It only mentions 'publishes by default' and implies mutation, but lacks details on reversibility, permissions, error handling, or impact of invalid patches.

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 concise (two sentences) and front-loaded with the core action. However, it could pack more useful guidance without becoming verbose.

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?

For a tool with 8 parameters, complex deep-merge behavior, and multiple identification methods (id, index, recId), the description is too brief. It omits explanation of match and textContains, and does not clarify how identification methods interact.

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 the description adds limited value beyond the schema. It explains 'deep-merge' and that null removes a field, which is helpful, but does not elaborate on identification strategy or edge cases.

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 'Change element(s) Zero Block' with a deep-merge JSON patch and lists modifiable properties (text, color, font, etc.). It is clear about the resource and action, but does not explicitly differentiate from sibling tools like zero_set_text.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., zero_set_text for text-only updates, zero_add_element for adding). There is no mention of prerequisites or contraindications.

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