flexsim_export_results

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

With no annotations, the description carries the full load. It usefully discloses one side effect (artifact_dir is created when missing) and a scope boundary (never touches PerformanceMeasures), but leaves out overwrite behavior for existing files, permission requirements, and rate/volume limits.

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?

Front-loaded with the core action, then a tight args block. The internal '_collect_statistics' detail is slightly obscure but earns its place as a scope boundary; overall no wasted sentences.

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?

An output schema exists, so return values need not be explained. But this is a write operation with zero annotations and a nested params object, and the description does not address overwrite semantics or error conditions, leaving meaningful gaps for correct invocation.

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%, so the description must compensate, and it does cover all four params with defaults (artifact_dir, format csv/json, filename snapshot.csv, statistics content/input/output basics). However it omits include_time and doesn't explain the objects/metrics structure, so a gap remains.

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?

States a specific verb (export) and resource (statistics snapshot), plus the output formats (CSV/JSON). The reference to reusing _collect_statistics and not touching PerformanceMeasures helps distinguish it from related statistics tools, though it never names the closest sibling flexsim_get_statistics directly.

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?

Usage is implied by 'export ... snapshot' and the note that it never touches PerformanceMeasures, which implicitly routes away from the performance-measure path. But it gives no explicit when-to-use vs flexsim_get_statistics or flexsim_chart_snapshot, and no prerequisites.

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