ee_cyber_get_guidance

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

With no annotations provided, the description must carry the behavioral burden. It clearly indicates a read-only 'get' operation and specifies the exact target resource. It does not describe error behavior or response format, but the simple fetch-by-reference nature is transparent enough; the verb 'Get' and resource phrasing provide the key behavioral context.

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, well-structured sentence that front-loads the action and resource, then adds high-value examples. No filler or redundant wording.

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 one-parameter retrieval tool with no output schema and no annotations, the description is nearly complete: it states what is returned and how to specify it. Minor omissions such as error handling or exact response format are acceptable given the low complexity and the clarity of the described operation.

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 provides 100% description coverage for the single parameter, so the baseline is met. The description goes beyond the schema by giving multiple concrete reference format examples ('RIA-ISKE-2023', 'RIA-juhend-001', 'CERT-EE-TG-2024-01'), which helps the agent understand expected syntax and naming patterns.

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 uses a specific verb ('Get') and resource ('RIA guidance document'), and clearly identifies the selection method ('by reference'). It distinguishes this tool from the sibling search tools by emphasizing retrieval of a specific known document rather than discovery or listing.

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 this tool should be used when the agent already has a document reference, and the examples reinforce that. However, it does not explicitly state when not to use it or mention that ee_cyber_search_guidance should be used when the reference is unknown, leaving the contrast with siblings implied rather than explicit.

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