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

The description adds little beyond the name and annotations. Annotations indicate readOnlyHint=false and destructiveHint=false, but no additional behavioral context (e.g., whether cancellation is reversible, idempotent, or requires special permissions) is disclosed. For a mutation tool, this is a significant gap.

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, front-loaded with the action, and no wasted words. Each sentence earns its place by stating the function and providing the source for the required ID.

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?

The tool is simple (one parameter, no output schema), and the description covers the operation and the parameter source. While it doesn't mention edge cases (e.g., canceling an already-finished workflow), the simplicity and sibling context make it reasonably complete.

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 0%, but the description compensates by explaining that workflowRunId can be obtained from workflow_info, which gives the parameter practical meaning. For a single self-explanatory string parameter, this is sufficient.

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 'Cancels' with the resource 'running EAS workflow', clearly distinguishing it from sibling tools like expo_build_cancel and expo_workflow_info. It also indicates the necessary context (a running workflow) without ambiguity.

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 provides clear context by stating the tool cancels a running workflow and explicitly instructs to use workflow_info to get the workflow run ID, which is an actionable prerequisite. It lacks explicit alternatives or when-not-to-use guidance, but the context is sufficient for this simple operation.

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