miro_list_all_items

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

The description discloses automatic pagination, a maximum of 10000 items, and provides a voice-friendly example. Since annotations already include readOnlyHint=true, the description adds further behavioral context (pagination behavior and limits) without contradiction.

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 extremely concise: three main sentences plus a usage phrase and a voice-friendly mock output. Every sentence provides necessary information, and the key action is front-loaded. No wasted words.

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?

Given the presence of an output schema and thorough annotations, the description is complete. It covers the tool's purpose, usage guidelines, behavioral traits (pagination, limit), and provides a sample output. No significant gaps.

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 baseline is 3. The description adds value by highlighting the automatic pagination and the max_items limit (up to 10000), which reinforces the parameter 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 it retrieves ALL items from a board with automatic pagination up to 10000, and explicitly contrasts with the sibling tool miro_list_items for quick lookups (max 50). This provides a specific verb+resource+scope and distinguishes from similar tools.

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 explicitly states when to use this tool ('get everything on board', 'list all items', 'export board contents') and when not to (for quick lookups max 50, use miro_list_items instead), providing clear guidance on alternatives.

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