miro_get_export_job_results

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

The description adds behavioral context beyond annotations: enterprise restriction, link expiration, and regeneration. Annotations already indicate read-only (readOnlyHint=true), which is consistent. No 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?

Two short, front-loaded sentences. First states purpose, second adds critical details. No filler.

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 key behavioral aspects (enterprise only, expiration) and the existence of an output schema reduces need to explain return values. However, it doesn't mention prerequisites like a completed job, which is slightly implied.

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 covers both parameters with descriptions ('Export job ID', 'Organization ID'). The description does not add further semantics, but schema coverage is 100%, so a baseline of 3 is appropriate.

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 retrieves download links for a completed export, using the verb 'Get' and specifying the resource 'download links for completed export'. It distinguishes from siblings like miro_get_export_job_status and miro_create_export_job.

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 key usage context: 'ENTERPRISE ONLY' and 'Links expire in 15 min; call again to regenerate.' It implies when to use (after export completion) and that expiration is handled by re-calling. It doesn't explicitly state when not to use or provide alternatives, but the guidance is clear.

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