qui_list_tracker_customizations

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

The annotation readOnlyHint=true already signals a safe read operation. The description adds no behavioral details beyond the call mechanics—no mention of return format, scope, permissions, or side effects. With annotations covering the safety profile, this is acceptable but minimal.

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, directly informative sentence. It is front-loaded with the endpoint and provides the necessary parameter-passing convention in a compact way, with every word adding value.

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 simple GET endpoint with no required parameters, the description covers the argument structure but omits any possible query parameters or path variable specifics. Since the output schema exists, return values need not be explained, but the lack of optional parameter details leaves a gap for the agent to know what filters might be available.

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 schema is a generic 'arguments' object with no property descriptions. The description significantly compensates by explaining exactly how to structure arguments: path variables directly, query values in arguments.params, and a JSON body in arguments.body. This is crucial operational guidance absent from 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 explicitly names the endpoint 'GET /tracker-customizations/' and the HTTP verb, making it clear this tool lists tracker customizations. It distinguishes from sibling create/update/delete tools by its GET method and collection resource.

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 does not explicitly state when to use this tool vs alternatives, but the endpoint and name imply it is for retrieving tracker customizations. It lacks explicit context like 'use this to list all existing customizations' or any mention of alternatives.

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