dhcp

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

With no annotations provided, the description must convey behavioral traits. The term 'Show' indicates a read-only operation, which is appropriate. However, it does not disclose any potential side effects, required permissions, or limitations such as lease filtering or refresh behavior.

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, efficient sentence with no extraneous information. It is front-loaded and to the point, making it easy for an AI agent to quickly grasp the tool's purpose.

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 simple show operation with one optional parameter and no output schema, the description is sufficient. It explains the core function, though it could mention typical output formats or what 'lease information' includes.

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 has 100% description coverage for the single parameter 'search', which already explains 'Search by hostname/IP/MAC'. The description adds no further meaning beyond the schema, so it meets but does not exceed expectations.

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 'Show DHCP lease information' uses a specific verb ('Show') and resource ('DHCP lease information'), making the tool's purpose immediately clear. It also distinguishes itself from the sibling tool 'dhcp_lease_delete', which is for deleting leases.

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 implies the tool is for viewing lease information, but it does not explicitly state when to use this tool versus alternatives like 'dhcp_lease_delete' or other network tools. No guidance on excluded cases or prerequisites is provided.

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