Bulk export plugin definitions

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

With no annotations provided, the description carries the burden and adds key behavioral traits: 'READ-ONLY' and 'High latency'. It also states that it returns full plugin records in bulk. However, it does not mention pagination details or export API specifics like continuation tokens, which would be useful for a high-latency bulk export.

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 concise and well-structured, with a clear primary statement, a usage preference note, and a behavioral note. Every sentence adds valuable information without redundancy.

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 presence of an output schema and the absence of annotations, the description provides solid context: what it does, when to use it, read-only safety, and latency expectations. It would be more complete if it mentioned how to handle the high latency (e.g., polling or long waits) and whether pagination exists, but for a bulk export tool this is reasonably sufficient.

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 0%, so the description must compensate for parameter meaning, but it does not explain `limit`, `search`, or `start_at`. The parameter names are somewhat self-explanatory, but the description's statement about needing the 'whole catalog' actually obscures the optional filtering parameters, leaving the agent without clear guidance on how to use them.

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 tool performs a bulk export of plugin definitions via Tenable OT's export API, with a specific verb ('export') and resource ('plugin definitions'). It also distinguishes itself from the sibling `query_plugin_definitions` by positioning this as the whole-catalog bulk option.

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 tells the agent to prefer `query_plugin_definitions` for interactive lookups and to use this tool when the whole catalog is needed. It also notes high latency, which further guides choice for non-interactive bulk operations.

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