market_ticket

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

With no annotations, the description carries full burden. It discloses OCR scanning and price comparison, and that submit_to_crowd persists validation. However, it does not mention authentication needs, rate limits, or potential side effects of submission, leaving gaps in behavioral understanding.

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 two sentences, front-loaded with the core purpose, and contains no fluff. Every sentence adds value: the first states the action, the second provides critical usage guidance.

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 no output schema and no annotations, the description should explain the return value or how results are presented. It lacks details on what happens after scanning and comparing (e.g., output format, next steps), making it incomplete for an OCR-based tool.

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%. The description adds context for 'url' ('Pass a public image URL') and 'submit_to_crowd' ('persist moat validation'), but does not enhance meaning for 'country' or 'line_items' beyond the schema. This adds marginal value over the schema, meeting baseline expectations.

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 scans a purchase receipt via OCR and compares prices against a 'data moat', using a specific verb and resource. It distinguishes from siblings like market_barcode (barcode scan) and market_compare (compare items) by focusing on receipt OCR.

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 tells how to use it ('Pass a public image URL', 'Set submit_to_crowd to persist') but does not explicitly state when to use this tool over alternatives or when not to use it. The '[Advanced]' tag hints at complexity but lacks concrete exclusions.

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