Update Content Block

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

Annotations declare readOnlyHint=false and idempotentHint=false, so this is a mutating, non-idempotent operation — the description correctly implies mutation. But it doesn't disclose what happens with dryRun behavior, whether updates are atomic, or what occurs when position is omitted vs combined with props. The dryRun parameter exists in schema but no behavioral context is provided.

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 sentences and reasonably concise. However, given 0% schema coverage and 6 parameters, it's under-specified rather than economically compact. The sentence is front-loaded with the purpose but lacks the depth needed for the parameter burden.

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?

With 6 params, 0% schema coverage, no output schema, and no annotation on mutation semantics, the description is insufficient. It names the action but leaves structural dependencies (portalRef/pageRef hierarchy), dryRun semantics, blocking behavior, and the relationship to kilango_move_block/reorder_blocks unexplained. For a tool performing two distinct behaviors (prop update and reordering), more context is needed.

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%, so the description carries full compensation burden. It only mentions 'props and/or move it (position)' and the index/before/after constraint. It doesn't explain what portalRef/pageRef/blockId refer to, what dryRun does, or the position object semantics beyond the constraint already stated. Critical identifiers like portalRef/pageRef/blockId are completely undocumented.

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?

Clear verb+resource+scope: 'Update a content block's props and/or move it (position).' It distinguishes props update from position change. However, it doesn't explicitly differentiate from sibling tools like kilango_move_block and kilango_reorder_blocks, which likely cover position changes — a meaningful differentiation gap.

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 says 'Position is at most one of index/before/after' which gives some usage constraint. But it doesn't explicitly say when to use this vs kilango_move_block or kilango_reorder_blocks, or when NOT to use it. Sibling tools suggest overlap on the moving functionality, and no guidance resolves this ambiguity.

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