Get FKC Scenario template

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

The annotations already declare readOnlyHint and idempotentHint, and the description ('Get details') is consistent with these. However, the description adds no extra behavioral context such as response format, authentication needs, or rate limits. With annotations covering the safety profile, a score of 3 is appropriate.

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 a single, front-loaded sentence with no unnecessary words. It is immediately clear what the tool does.

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?

The tool is simple but the description lacks important context: it does not specify what 'details' are included, how to find a template_id, or any guidance on usage. Since there is no output schema, the description should at least hint at the return structure, but it does not. The overall context is minimal.

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 input schema has no description for template_id (0% coverage), so the description must compensate. It only says 'specific template' without explaining the format of the ID or how to obtain it. The parameter name is self-explanatory to a degree, but the description provides minimal additional meaning.

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 ('Full Kill-Chain Scenarios template'), clearly distinguishing this tool from list_templates and other sibling get_template tools. It directly states what the tool does: retrieves details for a specific template.

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?

No guidance is provided on when to use this tool versus alternatives. Among the numerous sibling tools with similar names (e.g., cymulate_ev_templates_get, cymulate_bas_get_template, cymulate_advanced_get_template), there is no differentiation or context about when this specific FKC scenarios tool should be chosen.

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