listResponseTokens

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

No annotations are provided, so the description carries the full burden. It does disclose the return contents (built-in and custom tokens with active status) and 'Retrieve' implies a read-only operation, but it omits details like whether only active tokens are returned, pagination, auth requirements, or error behavior.

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?

A single front-loaded sentence with no filler: the verb and resource come first, followed by the inclusion criteria. Every word adds meaning.

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 zero-parameter list tool, the description conveys the core purpose and the contents of the result. However, with no output schema and no annotations, an agent is left without any expectation of the response shape, fields, or pagination behavior, so a bit more detail would make it fully self-sufficient.

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 tool has zero parameters and the schema coverage is 100%, so there are no parameter semantics the description must clarify. Per the baseline for 0-param tools, this dimension is adequately served.

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 uses a specific verb ('Retrieve list') and names the resource ('response tokens'), adding useful scope: built-in and custom tokens and their active status. It differentiates from sibling list tools like listProperties, listAudiences, and listOffers by naming the exact resource, though it doesn't explicitly contrast with the likely single-token sibling getResponseTokens.

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?

No when-to-use guidance is provided. The description never mentions alternatives such as getResponseTokens for fetching a single token, nor any exclusions or conditions that would route an agent to this tool over the many siblings in the same family.

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