execute-sp-api

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 discloses nothing about authentication needs, rate limits, error behavior, or the fact that GET/POST/PUT/DELETE have very different side effects (including destructive ones). For a generic API execution tool with mutation methods, this is a significant gap.

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 efficient sentence with no filler, appropriately front-loaded with the verb and resource. It is not padded, though it is arguably under-specified rather than genuinely concise.

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 7-parameter passthrough tool with nested objects, no output schema, and no annotations, the description omits nearly everything an agent needs: what the response looks like, what rawMode or generateCode actually change, and what auth/region setup is assumed. It is too thin for the tool's complexity.

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 the schema already documents endpoint, method, region, rawMode, parameters, generateCode, and additionalHeaders. The description only restates 'specified endpoint and parameters' and adds no format, constraints, or examples beyond the schema. 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?

The description states a specific verb (Execute) and resource (Amazon Selling Partner API requests), which is clear and materially more specific than the generic sibling execute-external-api. It does not explicitly contrast itself with explore-sp-api-catalog or execute-external-api, so it stops short of a 5.

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 choose this tool over execute-external-api or explore-sp-api-catalog, nor any mention of prerequisites such as credentials or the fact that this is a raw passthrough executor. Usage is left entirely to inference.

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