Canvas Node Connections

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

Annotations already indicate readOnlyHint, destructiveHint, and idempotentHint. The description reinforces 'Read-only' and adds valuable context about vault selection (session-active vs explicit vaultPath). No contradiction with annotations.

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 with two short sentences in the first paragraph and one in the second. Information is front-loaded and every sentence adds value without redundancy.

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 existence of an output schema, the description adequately covers purpose, usage, and vault selection. It does not need to explain return values. The description is complete for a focused graph-walking tool.

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?

Input schema covers 67% of parameters with descriptions. The description does not add explicit parameter details but explains the vaultPath behavior, which indirectly clarifies its purpose. This compensates for the missing schema description of vaultPath.

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 'Return the incoming and outgoing edges of a single canvas node' with a specific verb and resource. It distinguishes itself from the sibling 'canvas.parse' by noting a node-by-node approach versus full-graph parsing, and explicitly marks itself as read-only.

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 explicit guidance on when to use this tool ('walk the canvas graph one node at a time') and when not to ('for full-graph parsing, use canvas.parse'). It also explains vault selection behavior with clear alternatives and override logic.

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