ee_cyber_get_advisory

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

No annotations are provided, so the description carries full weight. It implies a read-only lookup with an exact reference but does not disclose behavior on missing/unknown references or describe the shape/content of the returned advisory. This is acceptable for a simple getter but leaves some edge-case behavior unspecified.

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 sentence with no filler, front-loading the action and target. It conveys everything necessary 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 single-parameter lookup tool with full schema coverage and no nested objects, the description is largely sufficient. The only minor gap is the lack of any mention of return contents or not-found behavior, which would be useful given there is no output schema, but the tool's simplicity keeps this from being a major omission.

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%, and the 'reference' parameter is already fully documented in the schema. The description adds only an example that duplicates the schema's example, so it adds no significant meaning beyond the structured definition.

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?

Description uses a specific verb ('Get') and resource ('CERT-EE security advisory') with a precise key ('by reference') and a concrete example. It is clearly distinct from sibling search tools like ee_cyber_search_advisories.

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 phrase 'by reference' makes the retrieval context clear: use when you already have an exact advisory ID. It does not explicitly name search_advisories as the alternative for queries without a reference, so it lacks an explicit when-not, but the intended usage is evident.

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