nsa_search_advisories

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

With no annotations, the description carries the behavioral burden; it discloses a 1-hour cache and states that results include extracted MITRE techniques, CVEs, and attributed actors. It does not mention rate limits, pagination, or error behavior, but the disclosed traits are material and go beyond the schema.

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 short and front-loaded, with the first sentence carrying the core purpose and the third adding useful behavioral detail. The second sentence is slightly redundant but not bloated.

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 two-parameter search tool, the description gives enough to invoke it correctly: source, accepted inputs, extraction behavior, and cache freshness. Without an output schema, a note on return shape would improve completeness, but it is not a blocker.

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 the schema already documents query and limit. The description's list of query types largely mirrors the schema's parameter description and adds no new semantic detail.

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 opens with a specific verb ('Search'), names the exact resource ('NSA Cybersecurity RSS feed'), and enumerates supported query types (keyword, CVE, actor name, malware family). This clearly differentiates it from sibling advisory-search tools by source.

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 NSA source is stated up front, giving the agent a clear context for when to invoke this tool. However, it does not explicitly name alternatives or state when not to use it, leaving some routing to inference.

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