miro_update_image_from_file

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

Annotations only provide a title; no behavioral hints. Description clarifies the operation is a replacement (destructive), requires the item to already exist, and requires the file to be on the local filesystem. Could be more explicit about side effects on the old file, but sufficiently transparent for the operation.

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?

Very concise and well-structured: front-loaded with core action, followed by usage guidelines, parameter list with brief explanations, notes, related tools, and a voice-friendly summary. Every sentence earns its place without redundancy.

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?

Covers purpose, usage, parameters, and related tools. With an output schema present, return values need not be described. Lacks explicit error handling or file validation details, but is otherwise complete for the tool's complexity.

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 is 100%, baseline 3. Description adds supported file formats for file_path (png, jpg, jpeg, gif, webp, svg) and clarifies parameter roles (e.g., title as alt text, parent_id as frame to move into), providing value beyond schema.

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?

Description states 'Replace the file on an existing image item with a new local image file,' providing a specific verb and resource. It distinguishes from siblings by explicitly naming miro_update_image (for metadata only) and miro_upload_image (for creating new images).

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?

Includes a 'USE WHEN' section with example user phrases and clear alternatives: 'For updating metadata only, use miro_update_image instead' and 'To create a new image from file, use miro_upload_image.' Provides precise context for tool selection.

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