pbs_metrics_servers_list

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

Discloses READ-ONLY nature and that the response is schema-enforced secret-free with no token field. Also mentions required PROXIMO_PBS_* config. With no annotations, the description provides useful behavioral insights beyond what is in the 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?

Two sentences, front-loaded with purpose and scope, no redundant information. Highly efficient.

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 tool's simplicity (one optional param, has output schema), the description covers key aspects: what it lists, the scope, safety guarantee, and config prerequisite. Complete for an agent to select and invoke correctly.

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?

Input schema covers the single parameter (proximo_target) with a detailed description. The description's mention of config requirement adds marginal context but does not significantly enhance parameter understanding beyond the schema.

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?

Clearly states the verb 'list' and resource 'ALL configured PBS metric servers', explicitly including both influxdb-http and influxdb-udp types in a unified view. Differentiates from sibling tools like pbs_metrics_influxdb_http_list and pbs_metrics_influxdb_udp_list which list each type separately.

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?

Implies usage for a unified view of both metric server types, but does not explicitly state when to avoid this tool or use alternatives like individual list tools. The sibling context provides implicit differentiation.

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