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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=true, so the safety profile is covered externally. The description adds no behavioral context of its own: it never states that existing text is overwritten, what permissions are needed, or what happens on an unknown itemId, so it contributes nothing beyond the structured hints.

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?

A single tight sentence with the verb and target list front-loaded and no filler. It is appropriately sized for the operation, though it is arguably too terse for the gaps it leaves.

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 destructive mutation with no output schema and two of three parameters undocumented, the description should say more about overwrite semantics, target validity, and selection versus siblings. As written, an agent has enough to attempt a call but not enough to invoke it confidently.

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 only 33% (boardId only), so the description must compensate for the undocumented text and itemId. It partially helps by naming the item types that itemId can address, but gives no guidance on text constraints (2000-char max) or itemId format, leaving a real gap.

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 gives a clear verb ('Change') plus the resource and enumerates the target types (note, text, shape, arrow label, frame name), so an agent can tell it edits text content rather than structure. It stops short of explicitly differentiating itself from siblings like edit_block or update_block, but the target list makes the scope reasonably distinct.

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 when-to-use guidance and no mention of alternatives such as edit_block or update_block, which plausibly overlap. Usage is only implied by the list of editable targets, leaving the agent to guess which tool to pick for a block edit.

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