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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered. The description adds genuinely new behavioral context: the actions run in the background, execute as the requesting person (impersonation/auth semantics), and the response returns before completion (async fire-and-forget). That async and identity behavior is exactly what the annotations cannot convey.

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?

Three short sentences, front-loaded with the core action, and each sentence adds a distinct fact (action, background/identity, async return). The opening 'Run a macro.' is mildly redundant with the following sentence but the rest earns its place.

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?

For a two-parameter mutation tool with full schema coverage, complete annotations, and no output schema, the description supplies the important missing pieces: asynchronous behavior and acting-as-the-requester semantics. It does not detail what the macro actions may alter, but the destructive annotation covers the risk signal.

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 100%, so both macro_id and conversation_ids are already documented in the schema, making 3 the baseline. The description's phrase 'on the conversations named' confirms the target but adds no format, ordering, or validation detail beyond the schema.

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 states a specific verb+resource ('Run a macro') and expands to what running entails: executing a macro's actions against named conversations. This clearly separates it from create_macro, update_macro, delete_macro, and list_macros, though it never names those siblings explicitly.

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?

There is no guidance on when to choose execute_macro versus the other macro tools, nor any prerequisites or exclusions. The only contextual hint is that it targets conversations already identified by the caller, which is implied rather than stated as usage guidance.

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