Load Rapid7 Parquet File

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

Annotations indicate idempotentHint=true and destructiveHint=false, which aligns with loading data. The description adds that it skips the export process and is faster. It does not mention error handling or file existence, but overall provides useful behavioral context.

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 three sentences, each adding value. No fluff. Purpose is front-loaded. It is concise and structured effectively.

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 simple tool with one parameter and an output schema, the description covers the main purpose, usage scenario, and speed benefit. It does not need to explain return values due to output schema. Complete for the given complexity.

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?

The single parameter 'parquet_path' has 100% schema coverage, baseline is 3. The description adds value by stating it can be a file or directory, which goes beyond the schema description. It clarifies the format.

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 tool's name and description clearly state it loads vulnerability data from Parquet files. The verb 'Load' is specific, and the resource is well-defined. It distinguishes itself from sibling tools like 'download_rapid7_export' and 'query_rapid7' by focusing on existing files.

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 explicitly says when to use: when you already have Parquet files and want to skip the export process. It mentions speed advantage. It could be more explicit about not using it if files are missing, but the context implies alternatives.

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