Block Update

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

No annotations are provided, so the description carries the full burden of behavioral disclosure for a mutation tool. Beyond the word 'Update', it says nothing about partial versus full updates, permissions required, side effects, reversibility, or what happens to omitted fields. This is a severe gap for an update operation.

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 extremely short, but it suffers from under-specification rather than conciseness. A single three-word fragment does not front-load useful information or earn its place by clarifying the tool's behavior.

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 five-parameter mutation tool with no annotations and no schema parameter descriptions, the description is completely inadequate. Although an output schema exists and need not be explained, the input side and behavioral expectations are left entirely to inference.

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% across five parameters (block_id, label, region, settings, visibility), and the description adds no parameter meaning at all. An agent cannot tell from the description what any argument does or how the nested settings and visibility objects should be shaped.

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 clear verb and resource ('Update a block'), so the basic action is identifiable. However, it provides no detail about what a block is in this context, which block types or fields are involved, or how it differs from siblings like block_create, block_delete, or layout_builder_update. The purpose is minimally viable but not specific.

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?

There is no guidance on when to use this tool versus alternatives such as block_create, block_delete, block_get, or block_place. The description supplies no context, prerequisites, or exclusions to help an agent choose correctly.

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