get_node_description

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

No annotations provided, so the description carries full burden. It discloses the read-only nature, return format (JSON with specific fields), error case, and a 4 KB cap. This is thorough for a simple read tool.

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?

Four well-structured sentences plus an Args list. Front-loaded with purpose, followed by usage and details. No redundant or missing information. Could be slightly more compact but efficient.

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 (2 params, read-only) and the presence of an output schema, the description fully covers purpose, usage, parameters, return format, error handling, and size limit. Nothing essential 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 coverage is 0% with no descriptions, but the description compensates by explaining id_mindmap as 'ID of the mindmap' and order_index as '1-based', adding meaning beyond the raw schema types.

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 'Read', the resource 'description of a single node', and the method 'by its order_index'. It distinguishes itself from siblings like get_mindmap_summary and get_mindmap by specifying a single node retrieval.

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?

Explicitly advises using this after get_mindmap_summary to avoid loading the entire mindmap, providing clear context. Does not explicitly list when not to use, but the guidance is strong.

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