firestarter_purchases

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

The readOnlyHint and destructiveHint annotations already mark it safe; the description adds test-environment-only limitation and live-key refusal behavior beyond the schema. It also clarifies that the refusal says nothing about Firestarter order history, which is useful contextual behavior.

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?

Three dense sentences front-load the core scope ('OFF-NETWORK purchases only') and each subsequent sentence adds a necessary distinction or caveat. There is no filler.

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 read-only list/get tool with fully described optional parameters, the description covers scope, exclusions, and environment behavior. It does not spell out the result shape, but this is not a blocker given the schema and read-only annotations.

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?

All four parameters have schema descriptions, so the schema carries the semantic load. The description does not add per-parameter meaning beyond what is already present.

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 identifies the tool as the pilot log of off-network purchases and explicitly distinguishes it from Firestarter order history, which lives in firestarter_status. This makes the tool's scope unambiguous relative to its siblings.

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?

It states the exact condition for use: off-network purchases recorded with firestarter_record_purchase, and explicitly says it is NOT for 'my orders' / 'order history', directing agents to firestarter_status. It also warns that live keys get a TEST_MODE_ONLY refusal, preventing misrouting.

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