iaas_get_request_trackers

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond repeating the path: it does not say whether results are paginated, unsorted, or potentially very large despite there being no filter parameters at all.

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?

It is short and front-loaded, but three lines say essentially the same thing twice ('Get request tracker' / 'Get all request trackers') plus the raw endpoint path. The repetition costs space without adding information.

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?

No output schema exists, so the description should hint at what a request tracker record contains or how many results to expect; it does neither. Still, the tool takes one optional parameter and the annotations cover safety, so an agent can invoke it without further detail.

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% for the single optional apiVersion parameter, so the schema does the explanatory work. The description adds no parameter meaning beyond that; the 3 baseline applies when the schema fully documents the inputs.

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 gives a specific verb and resource ('Get all request trackers'), and the HTTP path confirms it is the unfiltered collection endpoint. It does not distinguish this from the singular sibling iaas_get_request_tracker or from iaas_get_request_graph, which an agent would need in order to choose correctly.

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?

There is no guidance on when to use this versus iaas_get_request_tracker (fetch by ID) or iaas_get_request_graph. The only usage signal is implicit in the plural wording 'Get all', which is not enough given how many near-identical GET tools exist in this server.

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