firestarter_drop_requests

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description does not need to repeat safety. But the description adds crucial behavioral context: it reveals the requests are invisible to buyers and unclaimable until acted upon, and that they can expire on their own. It also discloses the content of the list (requesting community, listing, discount, claim count, deadline). This goes beyond annotations and helps the agent understand the state of the world, though it could mention what happens after expiry more explicitly.

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 single, dense paragraph that is front-loaded with the purpose and key constraints. Every sentence adds information: scope, behavior, content, and next steps. It avoids fluff and is well-structured for an agent to parse.

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 has no parameters, no output schema, and annotations cover safety, the description is complete for an agent to know what it does, when to use it, and what it returns. It even gives the call IDs (drop id) for follow-up tools. Nothing essential is missing.

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?

The tool has 0 parameters, and schema description coverage is 100%, so there is nothing to add. The description explains what the tool returns (the list of requests with specific fields), which is more valuable than parameter semantics. A baseline 4 is appropriate for tools with no parameters that clearly describe their output.

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 and resource ('List the community-sponsored drop requests waiting on YOUR decision as a seller'), and clearly differentiates from siblings like firestarter_approve_drop, firestarter_reject_drop, and firestarter_trust_community_drops. It fully explains the context and purpose of the tool, which is more than just restating the name.

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 this tool (to review requests waiting on your decision) and names alternatives (firestarter_approve_drop, firestarter_reject_drop, firestarter_trust_community_drops) for subsequent actions. It also states the condition (a community owner proposes a per-claim discount on one of your listings) and what the tool shows. This is strong guidance for an agent to choose and invoke it correctly.

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