List Sponsored Products campaigns

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

Description adds value beyond annotations: clarifies pagination mechanism (nextToken) and the nature of returned data (configuration, not spend/sales). No contradiction with readOnlyHint=true and openWorldHint=true.

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: first covers purpose and pagination, second provides critical usage guideline. No wasted words, front-loaded with key 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 5 parameters, no output schema, and good annotations, description covers purpose, pagination, and important distinction from metrics tools. Lacks example or return format but still adequate.

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 description coverage is 100%, so description adds little beyond schema. Mentions pagination token but doesn't elaborate on parameter meanings. Baseline 3 is appropriate.

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?

Description clearly states verb 'List', resource 'Sponsored Products campaigns', and specifies included fields (budgets, states, targeting type, dates). Distinguishes from sibling tools like create_report by stating it returns configuration, not metrics.

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?

Explicitly advises when not to use (for performance metrics, use create_report) and provides context about pagination with nextToken. Could mention alternatives for different ad types (sb_, sd_), but context from sibling names provides this implicitly.

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