Execute Tool

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

With no annotations provided, the description must carry the weight of behavioral disclosure. It only mentions the connection requirement; it does not disclose that executing actions may have side effects, mutate external systems, or what guarantees exist around execution. This is a significant gap for an 'execute' tool.

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 a single sentence that is front-loaded with the core purpose ('Execute an integration action/tool') followed by a critical prerequisite. There is no redundancy or filler, perfectly earning 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?

Given the tool has 3 parameters, a nested object, and an output schema, the description is minimal but adequate for a generic execution wrapper. It mentions the connection prerequisite but does not address error handling, long-running behavior, or side effects. The output schema covers return values, so that absence is less critical.

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 provides descriptions for all parameters (100% coverage), including 'action', 'timeout', and 'parameters'. The tool description itself adds no additional parameter-level meaning, so it relies on the schema. Baseline of 3 applies because schema coverage is high.

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 states the tool's function as 'Execute an integration action/tool', with 'execute' as a specific verb and 'integration action/tool' as the resource. This distinguishes it from siblings like 'search-tools' (searching) and 'list-connections' (listing), though it does not explicitly name those alternatives.

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 a key prerequisite ('Requires an active connection for the integration'), which implicitly guides when to use the tool. However, it does not explicitly state when to use this tool versus alternatives or add exclusion guidance, leaving usage largely inferred.

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