firestarter_reject_drop

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

Beyond the annotations, the description discloses concrete consequences: 'It never goes live, nothing is charged against your proceeds, and the requesting community owner is notified.' It also clarifies that the decision is one-off and that the community can ask again unless standing trust is revoked, which is valuable behavioral context not present in the schema or annotations.

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 sentences with no filler: the action is front-loaded, followed by side effects, then scope and the relevant 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 simple two-parameter rejection action, the description covers what happens, what does not happen, who is notified, and the boundary of the decision. No output schema exists, but the outcome is described well enough for an agent to invoke the tool correctly.

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%, so the schema already documents both drop_id and reason. The description repeats that drop_id comes from firestarter_drop_requests and that reason is optional and shown to the owner, but it adds no new parameter-level meaning beyond the schema.

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 a specific verb and resource: 'Decline a pending community drop request on one of your listings.' It also names the source collection (firestarter_drop_requests) and distinguishes the action from the standing-trust alternative, so an agent can tell it apart from siblings 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?

It clearly scopes the action to a single request and explicitly points to firestarter_untrust_community_drops for revoking standing trust, giving the agent a when-not-to-use signal. It does not explicitly mention the accept alternative (firestarter_approve_drop), but the context makes the decision boundary clear.

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