vet_sponsor_offer

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states that the tool returns checklists and mentions the overpayment-refund scam pattern, but it does not explicitly confirm that the operation is read-only or describe what the checklist contents include beyond the scam reference. However, the 'returns' wording implies a non-mutating action.

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 that is front-loaded with the primary action ('Returns green/yellow/red flag checklists') and then adds relevant context. Every phrase earns its place, with no filler or redundancy.

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 tool's simplicity (no parameters, no output schema, no annotations), the description sufficiently covers what the tool does and what to expect. It could be slightly more complete by fleshing out the types of flags included, but the mention of the overpayment-refund scam pattern provides a concrete example that anchors the tool's purpose.

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, so there is no parameter schema for the description to augment. The baseline for such cases is 4, and the description adds value by explaining the purpose of the returned checklists, which indirectly clarifies that no inputs are required.

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 ('returns') and resource ('green/yellow/red flag checklists') to clearly state what the tool does. It also specifies the target ('vetting an inbound sponsorship or brand-deal offer') and distinguishes itself from siblings by focusing on offer vetting and scam patterns.

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 clearly indicates when to use this tool: when an inbound sponsorship or brand-deal offer needs vetting. It does not explicitly name alternatives or exclusions, but the context is sufficiently defined for an agent to select it over sibling tools like interpret_pricing_model or get_negotiation_move.

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