create_dhcp_static_mapping

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

Annotations already declare readOnlyHint=false and destructiveHint=false, indicating a non-read-only, non-destructive write operation. The description adds no further behavioral context such as whether apply_immediately controls activation, duplicate handling, or effects on existing DHCP reservations. 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 a single, front-loaded sentence with a useful parenthetical clarification. It contains no filler or redundant words, making it appropriately concise.

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?

While the schema and annotations cover parameters and safety basics, the description lacks high-level context such as when to choose this tool, prerequisites (e.g., existing interface/DHCP pool), or the implications of apply_immediately=false requiring a subsequent apply_dhcp_changes. The presence of an output schema helps with return values, but these gaps make it only minimally 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 input schema provides 100% description coverage for all 9 parameters, including defaults and examples. The description itself adds no parameter-level detail, so with high schema coverage, a baseline of 3 is appropriate.

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 'Create a DHCP static mapping (reservation)' uses a specific verb and resource, clearly stating the tool's purpose. It distinguishes from sibling tools by action (create vs update/delete/search) and by resource (static mapping vs DHCP address pool).

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, prerequisites, or interaction with apply_dhcp_changes. The description merely states the action, leaving usage to be inferred from the tool name.

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