Check AMC execution status

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

Description adds the list of possible status values, which is helpful. Annotations already declare readOnlyHint and openWorldHint, so description adds modest additional context without contradicting.

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?

Single sentence, front-loaded with essential information, no wasted words.

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 no output schema and moderate complexity (4 params), the description is minimal. It covers the status values but lacks details about response structure or error conditions. Annotations provide safety context but not completeness.

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 50% (entityId and marketplaceId documented, instanceId and executionId not). The description does not provide additional parameter meaning for the undocumented ones, so it fails to compensate for the gap.

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?

Clearly states 'Check the status of an AMC workflow execution' with a specific verb and resource, and lists possible statuses. Distinguishes from sibling tools like amc_execute_workflow and amc_list_workflows.

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?

Implied usage (to check status after execution) but no explicit guidance on when to use vs alternatives, no when-not-to-use conditions.

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