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

Annotations already indicate readOnly and idempotent, and the description adds significant behavioral context: it always embeds mcpHandoffs, never requests vulnerability notes, instructs AI to keep notes local, and clarifies the 'significance' terminology versus CVSS/vendor severity. No contradiction with annotations.

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 front-loaded with the core purpose, and every clause adds useful information (payload contents, handoffs, privacy stance, version note). It is somewhat long but dense and well-structured; no wasted sentences.

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 no output schema, the description does an excellent job explaining what the tool returns: JSON payload, specific elements (brief section guidance, completeness criteria, significance, frameworks), and the handoffs array. It also covers the privacy behavior and version note, making it fully adequate for such a feature-rich tool.

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%, so parameter meanings are fully documented in the schema. The tool description does not add any parameter-specific detail beyond what the schema already provides, so baseline 3 is appropriate.

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 names a specific verb ('Load') and resource ('Lenny Zeltser's Vulnerability Investigation Brief context') and enumerates the payload contents (section guidance, completeness criteria, significance discipline, evidence sources, frameworks). It distinguishes itself from siblings by explicitly mentioning the mcpHandoffs array that points to other tools like rating_score_writing and cti_load_context.

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?

Clear context is provided: this is for loading the Vuln Brief context for local analysis, and the mcpHandoffs array tells the AI when to reach for alternative tools (e.g., rating_score_writing). However, it does not explicitly state when NOT to use this tool or directly compare with sibling load/template tools, so it stops short of a 5.

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