update_element

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

With no annotations, the description details updatable attributes and multi-session support, but does not disclose behavior like atomicity, error handling, or whether partial updates are supported beyond what the schema implies.

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, front-loaded with the main purpose, and uses a clear bullet-point list for attributes, making it easy to scan.

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?

Missing output description (no output schema), and no mention of what the tool returns upon success or failure. Adequate for a basic update tool but not fully complete.

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 schema already describes each parameter. The description adds a redundant list of updatable attributes and mentions multi-session support, but does not significantly enhance understanding 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 'Update attributes of an existing element' and lists specific updatable attributes, distinguishing it from siblings like delete_element or add_elements.

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 implicitly indicates use for modifying existing elements via the list of updatable attributes, but provides no explicit guidance on when not to use this tool or alternatives beyond the tool's own function.

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