firestarter_drop_requests

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'List' and no mutation language. It adds valuable behavioral context: requests stay invisible to buyers and unclaimable until approved/rejected or expired, and it describes what fields are shown. This goes beyond the annotations to explain the state and lifecycle of the listed items.

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 concise but information-dense. The first sentence states the purpose, the second lists the displayed fields, and the third gives actionable next steps. Every sentence earns its place without unnecessary fluff or repetition of the schema (which is empty).

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?

With zero parameters and no output schema, the description carries the full burden of telling the agent what to expect. It covers the request lifecycle, the displayed information (community, listing, discount, claim count, deadline), and the follow-up actions, making the tool fully understandable in isolation.

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?

This tool takes zero parameters, and the schema is an empty object (coverage 100%). Per the baseline for 0 params, no parameter semantics are needed. The description correctly focuses on the output rather than inputs, so this dimension is not applicable and scores a baseline 4.

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 this tool lists community-sponsored drop requests that require a seller's decision. It uses a specific verb ('List') and resource ('drop requests'), and explicitly differentiates from related tools by focusing on 'waiting on YOUR decision as a seller.' It also explains the context of per-claim discounts on listings, making the purpose unmistakable.

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 provides explicit usage guidance by naming follow-up tools: 'Use firestarter_approve_drop or firestarter_reject_drop with a request's drop id — or firestarter_trust_community_drops to stop reviewing this community's requests one by one.' This tells the agent exactly what to do after listing requests, and distinguishes this tool from alternatives.

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