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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds useful behavioral context beyond annotations: it specifies the data source ('Public-domain CISA CSAF data') and the exact contents of the response, setting expectations for what the call returns. No contradictions 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?

A single, tightly written sentence that front-loads the core action and then enumerates the return contents. Every word adds value; there is no fluff or repetition of schema properties.

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-only lookup tool with one well-documented parameter, the description fully covers what the tool does and what the response will contain. The absence of an output schema is compensated for by the explicit list of returned components. No critical information is missing.

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 schema already fully documents the single parameter with an example format, so description-level parameter guidance is not necessary. The description implicitly connects advisory_id to the advisory being fetched, but adds no extra semantic detail beyond the schema. Baseline of 3 applies due to 100% schema coverage.

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 verb and resource: 'Get full details of a CISA ICS/OT advisory' and enumerates the exact contents (affected products, CVEs with CVSS, summary, CSAF source URL). This clearly distinguishes it from sibling tools like search_ics_advisories (search vs. full detail) and get_cve_details (CVE-specific vs. advisory-scoped).

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 implies the tool is used when you have an advisory ID and need the complete advisory record, but it does not explicitly state when to use this over alternatives or mention that search_ics_advisories should be used to find IDs. The usage context is understandable but left to inference.

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