firestarter_reject_drop

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

Despite annotations (readOnlyHint=false, destructiveHint=false) already indicating this is a write operation with low destructiveness, the description adds valuable behavioral detail: the request never goes live, nothing is charged against proceeds, the requesting owner is notified, and the reason is optionally included. It also discloses the one-off nature of the decision and the distinction from revoking standing trust.

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, front-loaded sentences deliver the essential information without fluff. The first sentence states the action; the second covers side effects and notification; the third clarifies scope and an alternative. Every sentence earns its place.

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 tool with only two parameters, no output schema, and annotations already present, the description provides the necessary context: what the drop request is, that it remains pending, what happens on rejection, the optional reason, and how to block future requests. No critical behavioral aspect 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?

Input schema has 100% coverage: both drop_id and reason include clear descriptions. The description adds little beyond the schema—it mentions 'optionally with your reason' but the schema already says 'Optional short reason'. Since the schema carries the parameter meaning, the description's contribution is minimal but not detrimental.

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 opens with the specific verb 'Decline' and the resource 'pending community drop request on one of your listings', making the action unmistakable. It also references the source tool firestarter_drop_requests and distinguishes this from related actions like firestarter_approve_drop and firestarter_untrust_community_drops.

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 clearly states when to use the tool: to decline a pending request from firestarter_drop_requests. It also provides an explicit alternative by explaining that to prevent future requests from the same community, one should revoke standing trust with firestarter_untrust_community_drops, and it clarifies the scope ('this decides only this one request').

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