pve_sdn_prefix_list_entries_list

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

With no annotations provided, the description explicitly declares the tool as 'READ-ONLY', informing the agent that it is a safe, side-effect-free operation. No other behavioral traits are covered, but this is a critical disclosure.

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 extremely concise—two short sentences that convey purpose, safety, and workflow without any filler. Every word earns its place.

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?

Given the presence of an output schema and full schema parameter descriptions, the description is largely complete. It clearly states the tool's function and read-only nature. Minor improvement could be to explicitly say 'returns all entries', but it's adequate.

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 already provides complete descriptions for both parameters (100% coverage). The description does not add additional semantic nuance beyond what the schema offers, so baseline 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 clearly states 'READ-ONLY: list a prefix list's entries', specifying the verb (list), resource (prefix list entries), and scope. It distinguishes itself from siblings like pve_sdn_prefix_list_entry_create and pve_sdn_apply by mentioning them as alternative actions.

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 provides workflow context by advising to use pve_sdn_prefix_list_entry_create to add entries and pve_sdn_apply to commit changes. This helps the agent understand the sequence of operations, though it does not explicitly exclude use cases.

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