List Rapid7 Exports

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds that it returns metadata fields like export ID, date, status, type, and row counts, which is useful context beyond annotations. However, it does not disclose pagination, ordering, or time window for 'recent'.

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?

Only two sentences, front-loaded with the main action. Every sentence adds value without redundancy or unnecessary detail. Highly efficient.

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?

Given the tool's simplicity (single optional parameter, output schema exists), the description covers purpose, scope, and returned fields. However, it could clarify 'recent' (e.g., default time window) and note whether results are sorted. Overall adequate with minor gaps.

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% (limit parameter is well-defined). The description does not add any additional meaning or context beyond what the schema provides, resulting in a baseline score of 3.

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 clearly states the specific verb 'list' and resource 'Rapid7 exports', with scope 'recent' and 'tracked in the system'. It differentiates from sibling tools like check_rapid7_export_status or download_rapid7_export by focusing on listing metadata for available exports.

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?

Implicitly indicates use case ('useful for understanding what exports are available for reuse'), but does not explicitly mention when not to use or provide alternatives among siblings. No usage exclusions or context for when to choose this over other tools.

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