search_shaper_queues

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds that the tool supports filtering and pagination, which is useful behavioral context, but it does not disclose details like result ordering or any server-side limitations beyond what the schema implies.

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 that front-loads the primary action and resource. Every word contributes meaning: 'Search' indicates the verb, 'traffic shaper queues' the resource, and 'filtering and pagination' the key behaviors.

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 read-only search tool with a full input schema, annotations, and an output schema, the description sufficiently covers the core purpose. It does not explain return values, but the output schema covers that. It could mention whether any filters are mutually exclusive, but that is not necessary for basic use.

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 provides 100% coverage with descriptions for all four parameters, so the description does not need to explain them. The phrase 'filtering and pagination' generically aligns with the search_term and pagination parameters, but does not add any detail 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?

The description 'Search traffic shaper queues with filtering and pagination' clearly identifies the verb (Search), the resource (traffic shaper queues), and distinguishes this tool from sibling search tools like search_traffic_shapers by specifically targeting queues. The mention of filtering and pagination adds useful scope.

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 clearly implies the use case: when you need to find or list traffic shaper queues. It gives clear context but does not explicitly state when not to use it or mention alternative tools, so it falls short of a 5.

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