Download Rapid7 Export

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

Even though annotations carry idempotent/destructive flags, the description adds critical runtime behavior: it is a background operation that returns immediately, can take minutes for large exports, and requires polling for progress. This is exactly the kind of behavioral trait an agent needs beyond readOnly/destructive hints.

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, each earning its place: the purpose, the precondition, and the async behavior/follow-up. No redundant or vague 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?

For a 2-parameter async tool with full schema coverage and an output schema, the description covers the call ordering, the wait-time pitfall, and the polling mechanism. Nothing essential is missing for selecting and invoking it 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 export_id and export_type. The description references export_id in usage but adds no parameter-level nuance beyond the schema, so the baseline 3 is appropriate.

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 states a specific action ('Start downloading a completed Rapid7 export and loading it into the database') with a clear resource and lifecycle stage. It differentiates this from check_rapid7_export_status by explicitly referring to the completed-export precondition, and from start_rapid7_export by 'completed export.'

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 provides an explicit precondition: 'Call this after check_rapid7_export_status confirms the export is COMPLETE.' It also tells the agent what to expect (returns immediately) and how to follow up ('Poll progress with check_rapid7_export_status(export_id)'). This is clear, actionable usage guidance.

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