firestarter_request_escrow

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

Annotations are minimal (readOnlyHint false, destructiveHint false), so the description carries the burden. It discloses that Firestarter never contacts external sellers, that the agent must not automate messages, that a fetch is attempted but may fail on certain platforms, and that buyer_email is where the notification lands. This is rich behavioral context.

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 dense but well-organized paragraph, front-loaded with the decisive user-facing purpose. Every sentence adds needed operational detail (never automate, ask for title/price, platforms that block fetches). No 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?

For a 5-param tool with no output schema, this description covers workflow, failure modes, edge cases, and prohibited actions. The agent has all needed guidance to execute correctly, including how to behave when the fetch fails.

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 baseline is 3. The description adds value by clarifying the buyer-supplied nature of title/price, explaining the email's role, and specifying that title/price are needed because fetch may fail. It slightly exceeds the schema's own descriptions.

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+resource: 'Creates an escrow invite with a claim link for the SELLER, plus a ready-to-send message' for a buyer-side escrow request. It clearly distinguishes this from sibling tools (like firestarter_list for sellers, firestarter_execute, etc.) by framing it as the BUYER-side tool for external listings.

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 explicitly says when to use: when the user found a listing on another site and wants to pay through Firestarter escrow. It also provides exclusions: 'never automate messages to Craigslist or marketplace posters' and tells the agent to ask the buyer for title/price for platforms that block fetches. This is far beyond typical tool descriptions.

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