govt_joint_advisory_search

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

No annotations exist, so the description carries the full burden. It discloses the key behavioral trait that results are deduplicated by title, and it clarifies that the search runs across multiple agencies simultaneously. It also explains the real-world intelligence basis for the source's high confidence. A minor gap is the absence of return-shape or pagination details, but the core behavior is transparent.

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 compact and front-loaded: it states the core action and scope first, adds the selection-relevant confidence rationale, and closes with the deduplication behavior. Every sentence contributes useful information without redundancy.

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 simple read-style search tool with fully documented parameters, the description covers the essential selection and invocation context: source scope, deduplication, and confidence. Since there is no output schema, a bit more detail about the result fields would be ideal, but the description is still sufficient for an agent to call the tool correctly.

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 fully documents query, year, and limit. The description does not add parameter-level detail, but it also does not need to because the schema is complete. This meets the baseline for parameter semantics.

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 specific action ('Search for joint advisories') and a precise resource scope: Five Eyes agencies (CISA, NCSC-UK, ACSC, CCCS) simultaneously. It clearly distinguishes this tool from the many agency-specific sibling tools like cisa_search_advisories, ncsc_uk_search, acsc_search, and cccs_search.

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 description gives clear context for when this tool is appropriate: when joint advisories from multiple national agencies are needed, and it emphasizes their high confidence relative to other TTP sources. It does not explicitly state when not to use it or name individual agency search tools as alternatives, but the 'joint vs. individual' framing makes the intended use clear.

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