qui_get_tracker_icons

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

The readOnlyHint annotation already signals a safe read operation, and the description adds that it's a GET request and explains how arguments map to path, query, and body. This adds some behavioral context beyond the annotation, but does not cover response details, authentication requirements, or error conditions. No contradiction with 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?

Two sentences, front-loaded with the core purpose, followed by a compact instruction for argument construction. No redundant phrasing or filler.

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 has an output schema and a generic arguments object; the description covers the invocation pattern for path, query, and body, which is sufficient for a simple endpoint wrapper. However, it does not provide details on the specific parameters or expected payload for tracker-icons, so the agent must rely on external knowledge of the API.

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?

With 0% schema description coverage, the description compensates by specifying how the single 'arguments' field should be used: path variables directly, query values in arguments.params, and a JSON body in arguments.body. This gives essential meaning to an otherwise opaque catch-all parameter, though it does not enumerate the specific parameters accepted by the endpoint.

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 states the tool calls the GET /tracker-icons endpoint, naming both the HTTP method and resource. This is specific enough to distinguish it from sibling tools that target other qui endpoints, though it stops short of describing the functional outcome (e.g., 'list available tracker icons').

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 implies usage—whenever you need to interact with the tracker-icons endpoint—but it offers no explicit guidance on alternatives or conditions for use. The naming and endpoint path provide context, but there is no discussion of when not to use this tool or how it differs from other qui operations.

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