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

Beyond the read-only, idempotent, non-destructive annotations, the description discloses a privacy behavior (server never requests vulnerability notes and keeps data local) and clarifies that the 'significance' topic is distinct from CVSS/vendor severity scoring. These add meaningful context not captured by 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 moderately long but front-loaded with the core purpose, followed by a topical list and key usage notes. Every sentence earns its place, though the density of topics makes it slightly less concise than ideal.

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 tool's complexity and the absence of an output schema, the description covers purpose, topics, parameter relationships, and a notable privacy behavior. It does not explicitly describe the return format, but the guidance-focused nature is clear, making it adequately complete.

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 coverage is 100%, but the description adds value by explaining the relationship between topic and field_id, and by elaborating on several topic meanings (e.g., significance, actions, gaps). This enriches the parameter semantics beyond the schema descriptions.

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 retrieves Lenny Zeltser's expert vulnerability-brief writing guidelines, listing specific topics and explicitly distinguishing from sibling get_guidelines tools by domain (vulnerability briefs). The verb 'Get' plus the resource and scope make the purpose unambiguous.

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?

It provides specific usage guidance, such as pairing the 'fields' topic with field_id for single-field guidance, and implicitly indicates this is the tool for vulnerability-brief guidelines. However, it does not explicitly contrast with alternative sibling tools or provide exclusion criteria, so it falls short of full explicit guidance.

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