export_controls

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

With no annotations provided, the description carries the full burden. It states the action and source but does not explicitly disclose that the operation is read-only or whether it has side effects. 'Export' implies a non-mutating operation, but this is not stated, and the output format is not mentioned.

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 that is free of unnecessary words or technical jargon. It efficiently communicates the tool's purpose without any waste.

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 parameterless export tool, the description is nearly complete. It explains what is exported and the source, which is sufficient for an agent to decide when to call it. However, it does not specify the output format or whether a prior analysis is required, leaving a slight gap in expected behavior.

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 tool has zero parameters, and the baseline for this case is 4. The description adds meaning by clarifying what is exported (compensating controls) and from where (CyberSim analyses), which is useful context beyond the empty schema.

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 'Export' and specifies the resource 'recommended compensating controls' along with their source 'derived from CyberSim analyses'. This clearly distinguishes it from siblings like generate_report or sync_risk_register, which have different purposes.

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 usage in the context of CyberSim analyses but does not explicitly state when to use this tool versus alternatives. It lacks a clear when-to-use or when-not-to-use statement, leaving the agent to infer based on the name and siblings.

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