miro_update_text

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

The description's 'Update' terminology is consistent with the idempotentHint annotation. No additional behavioral traits are disclosed beyond the annotation, which is acceptable but adds no extra value.

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?

Description is concise with two lines. The first line effectively states purpose, but the second line (voice-friendly example) is marginal and could be removed for better conciseness.

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 mentions only a subset of parameters (content, font_size, color, position) while omitting others like text_align, width, and parent_id. Given the tool has 10 parameters and an output schema exists, the description should cover all updatable attributes.

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 for all 10 parameters. The description only lists parameter names without adding new meaning beyond what the schema already provides.

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 verb (Update) and resource (text element) along with specific attributes (content, font_size, color, position), distinguishing it from sibling tools that update other item types.

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 on when to use this tool versus alternatives like miro_update_shape or miro_update_sticky is provided. The description lacks context for appropriate usage scenarios.

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