miro_update_embed

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

The description does not disclose behavioral traits beyond the annotations. The idempotentHint annotation is present but not referenced. The description adds no information about error handling, side effects, or the effect of omitting optional parameters. The VOICE-FRIENDLY note is not behavioral.

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 concise with one sentence plus a VOICE-FRIENDLY note. It front-loads the verb and key attributes, but the structure could be improved (e.g., bullet list). There is no wasted text.

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?

The description covers the basic purpose but lacks context on behavior (e.g., that unspecified fields remain unchanged) and usage relative to sibling tools. An output schema exists, so return values are not needed. Given the tool's complexity (9 parameters), more context would be beneficial, but the description is minimally adequate.

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?

Input schema has 100% description coverage, so the schema already explains each parameter. The description repeats 'url, mode: inline/modal, dimensions, position' but adds no extra meaning. Baseline score of 3 is appropriate as the description provides no additional semantics beyond the 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?

The description clearly states the action 'Update' and the resource 'an embed', listing updatable attributes (url, mode, dimensions, position). It is specific but does not explicitly differentiate from sibling update tools for other Miro item types. However, the tool name itself implies the resource type.

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. There is no mention of prerequisites, exclusions, or context for choosing this over sibling tools like miro_update_card or miro_update_sticky.

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