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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior. The description adds useful context beyond annotations: webhook actions expose runtimeInputSchema, schedule/event actions set it to null, paused actions remain listed, and it does not start a run. Permissions are implied by 'this user can view', though auth/rate-limit details are not stated.

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?

The first sentence front-loads the resource and scope, and each subsequent sentence adds actionable behavior: pre-run use, runtimeInputSchema rules, paused-action edge case, and the fact that it does not start a run. There is no filler.

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?

An output schema exists, so the description need not detail return values, and annotations cover safety traits. It supplies the pre-call workflow, runtime-input distinctions, and paused caveat, which is complete enough for an agent to invoke it correctly.

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?

The tool has zero input parameters and an empty schema, so the baseline is 4. The description explains runtimeInputSchema as an output field for action configuration, but there are no input parameters needing clarification.

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?

States a specific verb ('List') and resource ('installed ProductNow actions this user can view'), including the user-viewable scope. The final sentence distinguishes it from run_action by clarifying that it does not start a run.

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 instructs to call this before starting an action so the agent knows each action's id and runtime-input needs, which ties it to run_action. It lacks a direct 'do not use if...' exclusion or named alternative, but the usage context is clear.

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