miro_update_image

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

Annotations provide idempotentHint but no readOnlyHint or destructiveHint. The description does not disclose behavioral traits beyond stating it's an update, lacking details on side effects, required permissions, or concurrency behavior.

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 very short with no redundant words. The two lines convey purpose and an example efficiently. Every part earns its place.

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?

Despite an output schema, the description lacks context about the effect of updating an image (e.g., replacement vs modification), failure conditions, or relationship to sibling tools. It is incomplete for a tool with 8 parameters and many siblings.

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 100%, so the description adds minimal meaning beyond listing field names. Baseline 3 is appropriate as the description summarizes but does not enhance parameter understanding.

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 states the tool updates an image and lists specific fields (title, url, position, width). However, it does not differentiate this tool from sibling tools like miro_update_image_from_file, which also updates an image but from a file source.

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 provides no guidance on when to use this tool versus alternatives, no prerequisites, and no context about appropriate usage scenarios. The voice-friendly example adds no usage guidance.

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