Drop Beacon

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

Annotations already indicate read-only, non-destructive, idempotent, and closed-world behavior. The description adds value by specifying what data is returned (prices, availability, links) and that it identifies the best price, but doesn't disclose additional behavioral traits like rate limits, authentication needs (beyond the optional api_key in schema), or error handling. No contradiction with annotations exists.

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 front-loaded with the core purpose in the first sentence, followed by specific return details and a key feature (best price identification). Every sentence adds value without redundancy, making it efficient and well-structured for quick understanding.

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 moderate complexity, rich annotations, and 100% schema coverage, the description is mostly complete. It explains the output format (prices, availability, links) and key behavior (best price identification), compensating for the lack of an output schema. However, it could improve by mentioning limitations or typical use cases relative to siblings.

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 description coverage is 100%, with clear documentation for both parameters. The description doesn't add meaning beyond the schema, as it doesn't explain parameter usage, constraints, or examples. Baseline score of 3 is appropriate since the schema adequately covers parameter semantics without extra description input.

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 specific action ('Compare prices'), target resource ('EDC product across multiple retailers'), and scope ('returns each retailer's current price, compare-at price, availability status, and direct product links'). It distinguishes from siblings by focusing on price comparison rather than availability checks, brand info, market trends, or product searches.

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 implies usage context through 'compare prices for the same EDC product' and 'identifies the best available price,' suggesting it's for price shopping. However, it doesn't explicitly state when to use this tool versus alternatives like 'check_availability' or 'search_products,' nor does it provide exclusion criteria or prerequisites beyond the required product parameter.

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