map_update_sticky

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

The description only indicates that a mutation occurs. With no annotations, it does not disclose side effects, error behavior, or that positional changes (x/y) are also possible, leaving the agent unaware of the full impact of the tool.

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 short sentence with no filler. It front-loads the operation and resource, making it easy to parse quickly.

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 mutation tool with no annotations and no output schema, the description is too sparse. It fails to mention the full set of updatable fields, including x/y coordinates, and does not differentiate from the sibling map_move_sticky tool, which may also handle position changes.

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 coverage for parameters is high; the description adds minimal semantic grouping (treating h and w as 'size') but omits x/y and text details. It does not contradict the schema but also adds little beyond it.

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 clearly identifies the operation ('update'), target resource ('sticky note'), and lists specific attributes (text, color, size). However, the input schema also allows changing x/y coordinates, which the description omits, creating ambiguity with the sibling tool map_move_sticky.

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?

No guidance is provided on when to use this tool versus alternatives like map_move_sticky or map_update_node. There is no mention of exclusions or the intended context for using this tool.

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