set_block_field

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

Annotations indicate the tool is a write operation (readOnlyHint=false), idempotent, and non-destructive, so the safety profile is already provided. The description adds nothing beyond the obvious 'set' action, but it does not contradict the annotations, so it meets a minimal standard given the annotation coverage.

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, front-loaded sentence with no extraneous words. It conveys the primary purpose immediately and wastes no tokens.

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 seven parameters, no output schema, and no parameter-level details, the description is far too sparse. It does not explain the confirm flag, the difference between 'input' and 'field' kinds, or the role of path and target, leaving critical gaps for correct usage.

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?

With schema description coverage at 0%, the description carries the full burden of explaining parameters. It mentions none of the seven parameters (kind, name, path, target, blockId, confirm, value), leaving the agent to infer their meaning from names alone, which is insufficient for correct invocation.

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 ('set'), a resource ('input param or dropdown field'), and a location ('on a block'), making the core action clear. It does not explicitly contrast with sibling tools like add_block or move_block, but the action is distinct enough that an agent can infer its purpose.

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 gives no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. It simply states what the tool does without context about appropriate scenarios.

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