apps__promoted_purchases__list

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

The description adds only the HTTP method and path, but does not disclose behavioral traits beyond the annotations (readOnlyHint, idempotentHint, destructiveHint). No information about pagination, rate limits, or response structure is provided.

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 sentence plus the endpoint. It is concise, front-loaded, and contains no wasteful 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?

Given the simplicity of the tool and the presence of annotations, the description is adequate but lacks explanation of pagination behavior implied by the 'limit' and 'next_url' parameters. The tool is straightforward, but some context is missing.

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 coverage is 100%, so the input schema already describes all parameters. The description adds no additional meaning about parameters beyond what is in 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 clearly states the action (List), the resource (promoted purchases), and the scope (belonging to an app). It also provides the REST endpoint, making the purpose unmistakable. It distinguishes from siblings like apps__promoted_purchases__replace.

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 for listing but does not explicitly state when to use this tool over alternatives like apps__promoted_purchases__replace. There is no guidance on prerequisites or context.

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