Cloud Outbound Manage Tool

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

With no annotations, the description fully discloses behavioral traits: save uses upsert semantics, delete cancels pending outbound actions, test counts against rate limits and budgets. It mentions middleware (ChannelRateLimit, TargetRateLimit) and recording as OutboundAction, giving the agent a complete picture.

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 description is well-structured with a clear introductory sentence followed by bulleted actions. It is slightly verbose but every sentence adds information. No fluff, but could be trimmed slightly for brevity.

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?

Given the tool's complexity (6 parameters, multiple actions, no output schema), the description covers all necessary aspects: action semantics, rate limits, upsert behavior, and destructive effects. An agent can confidently select and invoke the tool based on this description.

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 coverage is 100%, so the baseline is 3. The description adds value beyond schema by explaining save replaces existing connectors, delete is destructive, and test sends real payload. However, details on credentials and is_active remain schema-level only, so not a full 5.

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 clearly identifies the tool as managing outbound delivery connectors for messaging channels. It lists specific actions (list, get, save, delete, test) with brief explanations, and distinguishes the tool from siblings by focusing on connector lifecycle and channel types.

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 usage context for each action (e.g., 'save (write — upsert)', 'delete (DESTRUCTIVE)', 'test (write — sends a real test payload)'). It implicitly guides when to use which action but does not explicitly contrast with sibling tools like credential_manage or integration_manage.

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