export_iq_segment

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

With no annotations, the description bears full responsibility for behavioral disclosure. It states the tool saves to a local folder, but does not address potential side effects like file overwriting, permission requirements, or error handling. The behavior is minimally described.

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 wasted words. It could be slightly more informative without losing conciseness, but it is efficient and directly states the main action.

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 tool has 5 parameters, no annotations, and a minimal description, the context is incomplete. Key details about parameter meanings, output expectations, and usage constraints are missing. The tool's complexity warrants a more comprehensive description.

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 coverage is 0%, meaning no parameter descriptions exist in the schema. The description does not explain any of the five parameters (format, filename, num_samples, start_sample, workspace_dir), leaving the agent with no understanding of how to specify an 'IQ segment slice' or use defaults.

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 that the tool saves an IQ segment slice to a local folder. It uses a specific verb ('Saves') and resource ('IQ segment slice'), and distinguishes itself from siblings like export_plot and load_iq_file by specifying the output location and data type.

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 such as export_plot or load_iq_file. It does not mention prerequisites (e.g., having an IQ segment loaded) or when not to use it.

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