Update Block Settings

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

With no annotations, the description carries the full behavioral burden. It usefully discloses catalog validation and that values are written into the graph for later save/deploy, but it omits critical behavior around staged vs immediate mode, session prerequisites, and failure or permission 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 two tight sentences with the primary action front-loaded and a useful conditional side-effect note second. The inline JSON example is efficient and earns its place.

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?

This is a mutation-like tool with no annotations, 0% schema description coverage, and an important mode enum that is not described. The output schema reduces the need to explain return values, but the description remains incomplete for correct invocation.

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 0% for four parameters, so the description must compensate and largely does not. It gives an example for settings and hints at session context, but does not explain the mode enum values, session_id selection, or how block is identified.

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 a specific verb and resource: changing block settings in a running session, with a concrete settings example. It does not distinguish this tool from similar siblings such as set_parameters or get_block_settings, so the purpose is clear but not fully disambiguated.

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?

Usage is implied by 'in a running session' and the current-graph condition, but the description never explicitly says when to use this tool instead of set_parameters or get_block_settings. There are no stated exclusions or prerequisites beyond the vague current-graph note.

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