zwave_rebuild_node_routes

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

No annotations present. Description mentions return type and ValueError, but lacks side effects (e.g., network disruption, node must be awake, blocking nature). Minimal disclosure for a modifying operation.

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 plus code block for return. No wasted words; front-loaded with action and result.

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?

Tool performs a critical network operation but lacks context on triggers, prerequisites, and potential impacts. No output schema, though return documented. Incomplete for safe usage.

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%, description adds example 'e.g. 5' and clarifies it's a Z-Wave node id. Adds some meaning beyond schema's type, but still sparse.

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 verb 'Rebuild' and resource 'mesh network routes for a single node'. Distinguishes from siblings like zwave_begin_rebuilding_routes (all nodes) and zwave_rebuild_routes_status.

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?

No guidance on when to use this tool vs alternatives, e.g., when a node has connectivity issues. No prerequisites or context provided.

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