get_node

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

Description says 'Get' implying read-only, but annotations set destructiveHint=true, indicating potential side effects. This is a direct contradiction, leaving the agent uncertain about the operation's safety.

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 sentences front-loaded with purpose. No wasted words; efficient and clear.

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?

No output schema, but description notes 'full detail' without clarifying return structure. Contradictory annotations reduce completeness; adequate but could mention error handling or extent of detail.

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 covers nodeId parameter (100% coverage). Description adds valuable format guidance (colon format, avoid hyphens) that goes beyond schema definition.

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?

Description clearly states 'Get a single node by ID with full detail', specifying verb and resource. It distinguishes from sibling get_nodes_info which fetches multiple nodes.

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 get_nodes_info for multiple nodes to avoid repeated calls, and provides specific format rule (colon format, no hyphens).

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