list_dhcp_static_mappings

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

The description makes the read-only operation clear via 'List' and adds a behavioral/structural detail: each mapping carries parent_id representing its DHCP server/interface, and that value is reusable for deletion. No annotations are provided, but this disclosure is adequate for a simple list operation with an output schema.

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 concise sentences, with the core purpose front-loaded and the cross-tool usage tip in the second sentence. No filler or repetition of schema details.

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 one-optional-parameter list tool with an output schema, the description covers the operation and the only param's semantics. It could add an explicit 'returns all if interface is omitted' clarification, but the schema default already conveys that, so it is nearly complete.

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?

The schema provides only the name/type of interface with 0% description coverage, while the description gives its real meaning: a DHCP server/interface identifier taken from parent_id, used to filter the listing. This fully compensates for the bare schema.

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?

States a specific verb and resource: 'List DHCP static mappings (IP reservations)', with an optional interface filter. The parenthetical differentiates static reservations from sibling list_dhcp_leases, so the agent can select the right list tool.

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?

Clearly explains how to use the optional interface filter and connects it to the delete sibling by instructing the agent to pass each mapping's parent_id as the interface value. It does not explicitly enumerate when-not-to-use or alternatives, so it falls short of a 5.

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