get_tenable_cloud_vulnerability

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not state that this is a read-only operation, whether authentication or specific permissions are required, or any other behavioral traits beyond the bare 'Get vulnerability information' phrasing.

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 a single short sentence, so it is not bloated, but it is under-specified rather than efficiently informative. Every sentence should earn its place, and this one provides minimal actionable detail.

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 tool with one required parameter that is completely undocumented, plus no annotations, the description is not complete enough for an agent to invoke it correctly. The output schema covers return values, but the description should at least clarify the plugin_id parameter and distinguish this tool from its list-oriented siblings.

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% and the description does not mention the single required parameter plugin_id at all. It adds no meaning about what plugin_id represents or how it should be supplied, leaving the parameter entirely undocumented.

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 verb ('Get') and resource ('vulnerability information from Tenable Vulnerability Management'), but it is vague about what 'information' means and does not distinguish this tool from the sibling list_tenable_cloud_vulnerabilities. It also fails to indicate that this retrieves details for a single plugin given the required plugin_id.

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?

No guidance is provided about when to use this tool versus alternatives such as list_tenable_cloud_vulnerabilities or get_tenable_cloud_asset. The description gives no context, prerequisites, or exclusions.

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