Adh.Queries.List

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

No annotations are provided, so the description carries the full burden, yet it is a single sentence. 'List' implies a safe read, but there is no disclosure of pagination, result limits, ordering, or required auth scopes for a customer-owned resource.

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?

One efficient sentence with the resource and scope front-loaded and no filler. Brevity is appropriate, though it edges toward under-specification rather than optimal information density.

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?

An output schema exists, so return-value explanation is not required, and there is only one input parameter. Still, for a listing tool the description says nothing about pagination or result shape boundaries, and gives no hint about how these stored queries relate to the adh.query.* siblings.

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 single customer_id parameter has 0% schema description coverage, and the description only hints that it identifies the owning ADH customer. It adds slight meaning over the bare string schema but does not specify format (numeric ID vs. resource path) or whether it is the same customer identifier used by adh.customers.list.

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?

States a specific verb (List) and resource (stored analysis queries) scoped to an ADH customer, which is clearly distinct from the write-oriented siblings adh.query.create and adh.query.start. It stops short of explicitly contrasting with those siblings, so it is clear but not maximally differentiated.

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 adh.query.start, adh.query.create, or adh.jobs.get, nor any mention of prerequisites (e.g., that queries must have been saved first). Only the tool name implies usage.

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