firestarter_trust_community_drops

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

Annotations only say the tool is not read-only and not destructive. The description goes well beyond that by disclosing: standing approval is durable, pending requests are auto-approved, revocation only affects new requests, already-live drops remain, and discount costs still come from proceeds. That is strong behavioral detail.

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 dense but well organized: primary effect, triggering condition, reversal, caveat. It is slightly verbose and repeats the immediacy concept a few times, but every sentence contributes a meaningful behavioral point.

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 single-parameter state-changing tool with no output schema, this is nearly complete. It covers what the tool does, when to use it, what happens to pending requests, how to revoke it, the scope of revocation, and the financial consequence.

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 coverage is 100%, and the input schema explains program_id as the id from firestarter_drop_requests or the community owner. The description itself adds no extra parameter-level detail, so the baseline 3 applies.

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 explicitly states the verb and resource: 'Grant a community program standing approval to run drops on your listings.' It clearly distinguishes this from per-request approval tools and from the revocation tool 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 provides an explicit adoption condition — 'once you're comfortable a community's asks are reasonable' — and names the alternative for reversing the action. It tells the agent both when to use the tool and what the untrust sibling does differently.

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