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

With no annotations, the description carries the full disclosure burden, and it does state that the call returns full structure, nodes, and metadata, which is the key behavioral fact. It omits whether the operation is read-only, whether very large maps are truncated or paginated, and any permission requirements.

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 sentences, front-loaded with what is returned, followed by the one behavioral rule the agent must follow. Nothing is redundant and nothing buries the lede.

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 one-parameter read tool with a fully documented schema and no output schema, the description adequately summarizes the return payload and the required hyperlink behavior. Minor gaps remain around return format and handling of large maps, but nothing essential to invoking it correctly is missing.

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% and the single projectId parameter is thoroughly documented, including the URL-acceptance behavior and its state-recovery rationale. The description adds nothing about the parameter, so the baseline 3 applies.

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 gives a specific verb ('Get') and resource ('mind map') and names exactly what is retrieved: structure, nodes, and metadata. It is clearly the only read operation among siblings such as add_nodes, delete_nodes, and update_node, though it never explicitly frames itself as the retrieval counterpart to those mutators.

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?

Usage is only implied: an agent can infer this is the tool to inspect a map before or after mutations, but no explicit when-to-use, prerequisites, or alternatives are stated. The 'Always output the exact Canvas hyperlink' sentence is an output-handling directive, not guidance about when to select this tool.

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