Execute Program

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

Beyond the destructiveHint annotation, the description adds that the tool is NOT idempotent and will not be auto-retried. This provides useful behavioral context for the agent.

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 short sentences, each serving a clear purpose: defining the action and then adding key behavioral caveats. No unnecessary words, front-loaded with the action.

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 simple one-parameter tool with destructiveHint annotation, the description covers purpose, non-idempotence, and ID sourcing. It does not describe return values, but since there is no output schema, that is acceptable. A mention of success/failure could add completeness, but it is not essential.

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 input schema already describes the 'id' parameter with full coverage (100%), and the description reinforces the source of the ID ('Use list_programs to find program IDs.'), which adds helpful cross-reference context.

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 a specific verb ('Trigger') and resource ('an automation program on the CCU'), and distinguishes from sibling tools by referencing list_programs for finding program IDs.

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 states when to use (to trigger a program) and provides a warning about non-idempotence and no auto-retry. It also references list_programs for finding IDs. It does not explicitly mention when not to use, but the clues are sufficient.

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