search_interfaces

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safe read behavior is clear. The description adds minimal context beyond the annotations, only hinting at advanced search/filter capabilities without detailing behavior like pagination or result structure, but it does not contradict the annotations.

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 concise sentence, front-loads the main action, and contains no redundant words. It is appropriately sized for a simple search tool, though the 'advanced options' phrase is slightly vague but not wasteful.

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?

The tool is relatively simple with an output schema and annotations covering safety, but the description lacks differentiation from sibling tools and clarifications about what 'advanced options' means. This makes the description minimally viable but not fully complete for an agent to confidently select and invoke it.

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 100%, so the parameters are fully documented with descriptions. The description's mention of 'advanced options' does not add additional meaning beyond what the schema already provides, so the baseline 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 clearly states the tool searches and filters network interfaces, which is a specific verb+resource pair. However, the phrase 'advanced options' is vague and does not distinguish this tool from sibling search tools like search_interface_configs or find_interfaces_by_status.

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 no guidance on when to use this tool versus alternatives such as get_available_interfaces or find_interfaces_by_status. It also does not mention any exclusions or prerequisites, leaving the agent to infer usage from the vague 'advanced options'.

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