get_annotations

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

Discloses key behavior (scanning page when no nodeId) beyond the readOnlyHint annotation. No contradictions; adds useful context about operation scope.

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, first states purpose and output format, second covers both usage modes. No redundant words, efficient and well-structured.

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 simple read tool with one optional parameter and no output schema, the description fully covers necessary information: return type, parameter behavior, and usage modes.

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 parameter description (100%), but description adds value by explaining the effect of omitting nodeId (scanning current page). This meaningfully enhances schema information.

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 tool returns Dev Mode annotations in a specific structure, and distinguishes behavior with and without nodeId. It differentiates from sibling tools like scan_nodes or get_node.

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?

Provides clear guidance: use with nodeId for specific node, omit to scan page. While it doesn't explicitly exclude other use cases, the context is sufficient for correct tool selection.

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