miro_get_mindmap_node

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

The description adds value beyond the readOnlyHint annotation by noting it uses a 'v2-experimental API', which informs the agent of potential instability or differences. It does not contradict annotations and provides useful context about the tool's backend.

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: two short sentences with no redundant information. The first sentence states the core purpose, and the second adds the API version note. Every part is necessary and helps the agent understand the tool quickly.

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 tool's simplicity (two required params, output schema present, read-only annotation), the description is mostly complete. It could optionally mention that node_id is obtained from list_mindmap_nodes, but that's a minor gap. The experimental API note adds important context.

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?

The input schema already has 100% description coverage for both parameters (board_id and node_id). The description does not add additional meaning or clarify parameter formats beyond what the schema provides, which is acceptable given the high coverage.

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 'Get' and the resource 'mindmap node', and specifies the details included (content, hierarchy, position). It effectively distinguishes itself from sibling tools like miro_create_mindmap_node and miro_list_mindmap_nodes by indicating it retrieves a single node's details.

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 does not provide explicit guidance on when to use this tool versus alternatives. However, the purpose is clear enough that an agent can infer its use for retrieving a specific node's data, while listing or creating nodes are handled by siblings. No explicit when-not-to-use or alternative tool references are provided.

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