get_node

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description adds significant value by disclosing token estimates for each detail level (e.g., ~200 tokens for minimal, ~1-2K for standard), output types per mode (e.g., markdown for docs), and combining parameters. No contradictions.

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 concise and front-loaded with the core purpose. Each sentence adds unique information: overview, detail/mode explanations, and usage tips. No redundant or vague statements.

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?

The description covers modes, detail levels, token costs, and parameter combinations well, but it doesn't explicitly describe the overall output format (e.g., JSON structure for standard info mode). Given no output schema, a brief mention of return shape would improve completeness.

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?

Despite 100% schema coverage, the description adds meaningful context beyond parameter descriptions, such as token size expectations for detail, usage examples (e.g., 'Use format='docs'), and combining mode with propertyQuery. This helps the agent make informed parameter choices.

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 'Get node info' with specific verb and resource. It details progressive detail levels and multiple modes (info, docs, search_properties, versions, etc.), which distinguishes this tool from siblings like get_template or search_nodes. The purpose is unambiguous and well-defined.

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 provides internal usage guidance (e.g., 'Use format='docs' for readable documentation, mode='search_properties' with propertyQuery for finding specific fields') but does not explicitly address when to use this tool versus sibling tools like search_nodes or get_template. Missing cross-tool alternatives.

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