pbs_acme_plugins_list

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

With no annotations provided, the description carries full burden for behavioral disclosure. It explicitly warns that the result includes the raw credential blob and must be handled as sensitive, and declares the tool is read-only. This goes beyond what the input schema provides.

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 sentences with no filler. It front-loads the critical 'READ-ONLY' label and sequentially adds purpose, sensitive data warning, and configuration requirement. Every sentence adds value.

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 list tool, the description covers the core functionality, sensitive data handling, and configuration requirement. The presence of an output schema means return values are predefined. It doesn't mention pagination or filtering, but those are likely unnecessary for a simple list. Slightly incomplete due to lack of result format hints, but still good.

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 description does not add information about the single parameter (proximo_target) beyond what the input schema already provides. With 100% schema coverage, the baseline score 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 uses a specific verb ('list') and resource ('configured PBS ACME DNS challenge plugins'), clearly distinguishing it from sibling tools like pbs_acme_plugin_get, create, delete, update. It also includes important detail about including the raw credential blob, which sets it apart from other list tools.

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 begins with 'READ-ONLY', guiding the agent to use it when a safe read is needed. It also states 'Needs PROXIMO_PBS_* config', setting prerequisites. While it doesn't explicitly mention when not to use it or alternatives, the naming and sibling context make usage clear.

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