get_mcp_capabilities

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

No annotations are provided, so the description carries the full disclosure burden, and it adds essentially nothing: it does not say the call is read-only, that it has no side effects, or that it returns a catalog of tools/capabilities. For a zero-parameter meta tool the risk is low, but the description contributes no behavioral context beyond the name.

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?

A single front-loaded sentence with no filler or redundancy. Every word earns its place and the object of the action comes first.

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?

With an output schema present, the description need not explain return values, and a zero-param tool needs little parameter detail. However, for a meta/discovery tool that exists to orient an agent, the omission of any 'call this first / use this to discover available tools' guidance leaves a real gap.

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 tool takes zero parameters, so the baseline of 4 applies and there is nothing for the description to clarify. Schema coverage is nominally 100% on an empty property set.

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 gives a clear verb ('Show') and a specific resource ('capabilities available through the Tenable Security MCP server'), which is unambiguous and readily separable from the concrete vulnerability-management siblings. It stops short of explicitly contrasting itself with any sibling, but the meta/introspective nature is evident.

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?

There is no statement of when to call this versus the other 30 tools, nor any suggestion that it is a discovery/introspection entry point. The intent is only inferable from the tool name, not from the description text.

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