list_dhcp_leases

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context by distinguishing substring matches from exact matches against RouterOS lease-time, which is not present in the annotations or 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?

The description is two short paragraphs, front-loads the core purpose, and uses the notes only for non-obvious filter matching behavior. Every sentence earns its place without repetition or filler.

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 read-only list tool with an output schema and safety annotations, the description is partially complete: it explains filter matching semantics but omits several parameter meanings, filter combination logic, and expected value formats. It is callable, but avoidable ambiguities remain.

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% across 10 parameters, so the description carries the full burden. It only explains matching semantics for address/identity filters versus server/status/lease-time filters, leaving device, last_seen_within, class_id_filter, hostname_filter, client_id_filter, and all value formats undocumented.

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?

Starts with a specific verb and resource: 'Lists detailed IPv4 DHCP leases'. The IPv4 and 'leases' scoping clearly distinguishes it from siblings such as list_dhcpv6_bindings, list_dhcp_servers, and list_arp_entries.

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 gives useful context for optional filtering, but does not state when to choose this tool over alternatives like list_dhcpv6_bindings, list_dhcp_servers, or list_arp_entries. No explicit when-not guidance or prerequisites are provided.

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