afg2125_configure_am

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

Annotations are all false, so the description must disclose behavior. It adds the prerequisite but doesn't explain side effects or what happens if the condition is not met. It also doesn't clarify how configuration interacts with existing settings.

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?

One sentence with no filler. The prerequisite is integrated efficiently.

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 tool with four unannotated parameters and no schema descriptions, the description is too sparse. It doesn't define the parameters or discuss behavior when expectations aren't met.

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 schema has 0% description coverage and the description doesn't mention any parameters. It offers no explanation of source, depth_percent, modulation_function, or modulation_frequency_hz beyond their names and 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 uses the specific verb 'Enable and configure' with resource 'AM', clearly indicating the tool sets up AM modulation. It is distinct from sibling tools like set_am_enabled, though it doesn't explicitly call them out.

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?

It states a prerequisite: 'MAIN output must already be disabled.' This gives clear context for when to use the tool. However, it doesn't mention alternatives 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.