create_sp_targets

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

No annotations exist. The description labels it as a 'guarded write' and mentions preview vs. create, but lacks details on side effects, authentication, rate limits, or what 'guarded' implies. Critical for a write operation.

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 extremely concise at two sentences, front-loaded with the purpose. Every word serves a function; no unnecessary fluff.

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 optional parameters and no output schema, the description omits crucial context: how preview and dry_run relate, the format of 'changes,' and expected responses. The introspection stub note is helpful but insufficient for an agent to use the tool effectively.

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% with parameter descriptions. The description adds minimal value beyond the schema, such as grouping 'preview' and 'dry_run' as similar but not clarifying their relationship. Baseline score due to high schema coverage.

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 tool previews or creates Sponsored Products targeting clauses, distinguishing it from sibling tools like create_sp_negative_targets. However, it could be more specific about what 'targeting clauses' are.

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 provides no guidance on when to use this tool versus other create_ tools. It mentions it's a 'hosted endpoint only' and an 'introspection stub,' but that is a technical constraint, not usage advice.

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