miro_get_tag

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

The description reveals the tool is a read operation, which aligns with the readOnlyHint annotation. No contradiction. However, it adds minimal behavioral context beyond the annotation, such as what fields are returned or any error handling, though output schema exists.

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: one sentence plus a short voice-friendly example. No superfluous words, every part adds value.

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?

For a simple get-by-ID tool with good schema, annotations, and output schema, the description is mostly complete. It covers the basic purpose and parameters, but lacks guidance on error handling or what happens if the tag doesn't exist.

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% with clear parameter descriptions ('Board ID', 'ID of the tag to retrieve'). The description does not add meaning beyond the schema, so baseline score 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 'Get details of a specific tag by ID', using a specific verb and resource. It distinguishes from sibling tools like miro_list_tags (list all tags) and miro_get_items_by_tag (get items by tag), making its purpose unambiguous.

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 implies usage for retrieving a single tag's details by ID, but does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives like miro_list_tags for listing all tags.

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