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

Discloses that API actions run synchronously, browser actions return outcome='queued' with a ticket_id to poll, and that while pending there is no sub-status. Also notes that additionalProperties in inputs are rejected.

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?

Front-loaded with the main purpose, each sentence adds value with no redundancy. Concise yet informative.

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?

Output schema exists so return values need not be explained. Covers behavior and distinctions from siblings, but could mention the purpose of the executor parameter.

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?

With 0% schema coverage, description compensates by explaining that inputs must match the action's input_schema exactly and that additionalProperties are rejected. However, it does not detail the executor or action_id parameters beyond what schema provides.

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 it invokes a single action with typed inputs, and distinguishes from sibling actionlayer_start_task by specifying that envelope metadata belongs in the latter.

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 tells when to use this tool versus actionlayer_start_task, and explains synchronous vs async behavior with polling instructions.

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