asuswrt_dhcp_reservation

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

The description mentions multiple actions including mutation (add, remove) but does not disclose behavioral traits beyond what the name implies. No annotations exist, so the description should cover safety, confirmation requirements, or persistence of changes, but it does not.

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 a single sentence with no wasted words, but it lacks structure (e.g., no bullet points for actions or parameter relationships). It is concise but fails to provide essential detail, earning a mid-range score.

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 tool with multiple actions, 6 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain return values, error cases, or how to properly invoke each action, leaving the agent under-informed.

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 description coverage is 0%, and the description does not add any meaning to the parameters. Of the 6 parameters (action, mac, ip, name, confirm, dry_run), only 'action' is implied. The agent receives no help understanding required constraints (e.g., which fields are needed for add vs remove).

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's verb (List, add, or remove), resource (DHCP static reservations), and method (via SSH NVRAM). It effectively distinguishes this tool from the many sibling tools covering other ASUSWRT functions.

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 is provided on when to use this tool versus alternatives (e.g., asuswrt_dhcp_leases, asuswrt_dhcp_config). There are no prerequisites or warnings about side effects, leaving the agent to infer usage context.

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