Execute AMC workflow (async)

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

Description communicates the async nature and non-destructive behavior, aligning with annotations (readOnlyHint=false, destructiveHint=false). Adds the polling pattern and result retrieval workflow, going beyond the annotations.

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 sentences, no wasted words, front-loaded with verb and resource. Perfectly concise.

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?

Provides the essential workflow: execute, poll, fetch results. However, missing details on error handling, prerequisites (e.g., saved workflow exists), and the role of instanceId. With no output schema, the description covers the basic flow adequately.

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?

Description mentions 'over a time window' related to time parameters but does not explain key parameters like instanceId and workflowId, despite schema coverage only 57%. Schema descriptions exist for entityId, marketplaceId, timeWindowStart, timeWindowType, but the description adds little parameter-level detail.

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?

Description clearly states 'Start an execution of a saved AMC workflow over a time window' with a specific verb and resource, and distinguishes from siblings like amc_get_execution (polling) and amc_get_download_urls (fetching results).

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?

Explicitly describes the async pattern: 'Returns an execution id; poll with amc_get_execution, then fetch results with amc_get_download_urls.' This provides clear context on when to use this tool (to start an execution) and the subsequent steps, though lacks explicit alternatives or when-not-to-use guidance.

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