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

Goes well beyond the annotations: clarifies that the destructiveHint covers only the staged upload (no file move, no status/mapping-state change), that the existing segment survives cancellation, that the call is idempotent, and that 'creator' scope is required. This resolves the ambiguity an agent would otherwise have about destructiveHint=true.

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?

Front-loaded with the action and trigger, and every sentence carries information (behavior, alternatives, idempotency, param exclusivity, auth). Slightly dense at six sentences, but there is no filler.

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?

An output schema exists, so return values need not be explained. Given that, the description covers everything an agent needs: trigger, side effects and non-effects, post-cancellation handling, idempotency, parameter selection, and auth scope.

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 descriptions already cover both params, but the description adds a rule the schema does not enforce: pass exactly one of segment_id or audience_id, and that audience_id resolves server-side to the matched member segment. Useful added semantics beyond the 100%-covered 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?

States a specific verb and resource: abort a staged matched-segment upload. Explicitly ties itself to the analyze_audience_upload workflow, making it distinguishable from generic cancel/delete siblings like archive_segment.

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?

Names the exact trigger (user declines to proceed after reviewing analyze_audience_upload results) and routes the agent to alternatives: get_segment to inspect, archive_segment if the retained segment is no longer needed. When-to-use and when-to-use-something-else are both covered.

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