search_haproxy_backend_servers

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. However, the description adds zero behavioral context beyond that, such as how search works, pagination behavior, or that parent_id is required. It doesn't contradict annotations, but it also provides no added value.

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, straightforward sentence with no fluff. It conveys the core purpose in 7 words, which is appropriately concise. It's under-specified but not verbose.

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 simple search nature, the complete schema, and the presence of an output schema, the description is minimally sufficient but not rich. It lacks usage context and any guidance on how to find servers for a specific backend, though the required parent_id hints at this. Could be more complete with a note like 'requires backend ID' or a pointer to manage_haproxy_backend_server for modifications.

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 coverage is 100%, so the baseline is 3. The description doesn't mention any parameters or provide additional context beyond the schema, so it neither helps nor hinders. The schema already documents all 5 parameters clearly.

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 states the specific action (search) and the resource (servers within an HAProxy backend), which clearly distinguishes it from sibling tools like search_haproxy_backends or search_haproxy_frontends. It doesn't explicitly contrast with them but the scope is unambiguous.

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?

No guidance is provided on when to use this tool vs alternatives, prerequisites (e.g., needing a backend ID), or any exclusions. The description only says what it does, not when to use it.

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