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

Annotations already signal readOnlyHint=false and destructiveHint=true, and the description adds meaningful behavioral context: every call is recorded as an integration event and the task's client determines which workspace is reachable. This goes beyond the structured annotations and warns the agent about side effects and prerequisites.

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 compact and front-loaded: it states the core function in the first clause, supplies varied concrete examples, and then gives the essential usage preconditions. Every sentence earns its place without redundancy or 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?

For a generic integration executor with no output schema, the description covers the critical operational context: lease requirements, workspace routing, event recording, and the need to inspect available connections first. It does not describe response shape or error behavior, but those are provider-dependent and less essential than the stated preconditions.

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 parameters are already well-documented in the input schema. The tool description adds examples of actions but does not provide additional semantic meaning for body, query, or method beyond what the schema already states. A baseline 3 is appropriate.

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 phrase ('Perform one call against a system this client has connected') and gives concrete examples such as posting a Slack reply and reading a Linear issue. It clearly differentiates this execution tool from list_integrations and from the many task-management siblings by framing it as the generic integration invocation tool.

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 explicitly states preconditions ('must hold an active lease') and directs the agent to 'Call list_integrations first to see what is connected.' It does not explicitly enumerate when not to use this tool versus other alternatives, but the context and the call to list_integrations make the intended usage clear.

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