fa_create_alert

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

The description adds critical transparency beyond annotations: it reveals the dry-run behavior and that no network call is made without confirm. Annotations only indicate non-read-only and non-idempotent, but the description clarifies the exact side-effect conditions.

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?

Two concise sentences, front-loaded with the tool's purpose. Every word adds value with no redundancy.

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 15 parameters but full schema coverage and no output schema, the description covers the essential behavioral difference. It could mention what the dry-run preview returns or the response structure upon creation, but remains adequate.

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 100% with individual parameter descriptions. The description adds value by explaining the overarching role of the confirm parameter and the preview vs creation flow, which is not obvious from the schema alone.

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 starts with 'Create a flight alert on your AeroAPI account,' which uses a specific verb and resource. It clearly distinguishes from sibling tools like fa_delete_alert and fa_update_alert by focusing on creation.

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 explicitly explains the dual behavior: without confirm it is a dry-run preview, with confirm it creates the alert. This provides clear context on when to use each mode, though it lacks guidance on alternatives like update or delete.

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