Export Community Member Charges

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

Annotations declare readOnlyHint=false, destructiveHint=true and idempotentHint=false, so the agent knows this mutates. The description adds a valuable, non-obvious disclosure that an 'export' actually changes community state and requires an explicit confirm=true, reconciling the surprising safety profile. It stops short of saying what state is changed or whether the export is reversible.

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?

Two sentences, appropriately short and front-loaded, but the first is pure title repetition and earns no place. The behavioral warning is placed second, which is reasonable, but half the description is redundant.

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 20 optional parameters and no output schema, the description leaves the agent without any sense of what the export returns (presumably a CSV governed by the fields parameter) or how the result is delivered. The critical confirm/state-change behavior is covered, so it is minimally complete but not rich.

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 all 20 parameters (fields, status, date filters, amount bounds, etc.) are already documented in the schema. The description adds no syntax, format, or defaulting detail beyond it. Baseline 3 applies when the schema carries the full parameter burden.

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 first sentence is a verbatim restatement of the title ('Export Community Member Charges'), which is tautological. The second sentence adds that it is a state-changing operation, which is genuinely informative, but the description never distinguishes this tool from the very similar sibling export_community_member_subscriptions or from list_charges. Purpose is discernible but not differentiated.

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 gives one concrete usage rule — confirm=true is required, and only when the user asked for exactly this action — which mirrors the schema's confirm description. However, there is no guidance on when to choose this export over export_community_member_subscriptions or list_charges, and no prerequisites or filtering context.

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