Get Advanced Scenarios assessment result

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

Annotations already declare readOnlyHint and idempotentHint, and the description aligns with those. However, it adds no additional behavioral context beyond what annotations provide—no mention of result format, pagination, or prerequisites. The description is essentially a restatement of the title.

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, concise sentence that directly states the tool's purpose without any redundant or irrelevant information. It is appropriately front-loaded and easy to parse.

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?

Given the simple one-parameter input and the presence of readOnly and idempotent annotations, the description is minimally adequate. However, without an output schema, it could benefit from clarifying what 'results' includes (e.g., raw data, summary, or report format) and whether any assessment state is required.

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 0%, and the description does not explain what assessment_id is, where to find it, or its expected format. The phrase 'specific Advanced Scenarios assessment' minimally connects the ID to the resource, but it does not compensate for the complete lack of parameter documentation.

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 clearly states the action (Get) and the resource (results for a specific Advanced Scenarios assessment). It distinguishes from sibling tools like cymulate_advanced_get_findings and cymulate_bas_get_latest_results by specifying the exact assessment type and result scope.

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 provides no explicit guidance on when to use this tool versus alternatives such as get_findings or list_assessments. It only implies usage through the phrase 'specific Advanced Scenarios assessment,' but lacks context on prerequisites or exclusions.

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