tealfabric_execute_integration

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

No annotations are provided, so the description carries the full disclosure burden, yet it never says what execution actually does: whether it fires an outbound call to a connected system, whether it has side effects, whether it is retryable, or what happens on failure. The async flag is mentioned but its semantics (queued, returns immediately, no result) are not explained.

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?

It is a single front-loaded sentence with no padding, but the brevity comes at the cost of substance rather than being efficient compression. Nothing is wasted, yet almost nothing is contributed.

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 side-effecting execution tool with no annotations and no output schema, the description should cover return shape, failure behavior, and async implications. None of that is present, leaving the agent materially under-informed before invoking.

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 schema already documents integration_id, data, and async. The description adds no meaning beyond restating 'optional async' and 'optional call data', which is the baseline expectation when the schema does the work.

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 names a verb ('Execute') and resource ('integration'), but 'Execute an integration' essentially restates the tool name tealfabric_execute_integration. It does not distinguish this tool from sibling tealfabric_execute_process or tealfabric_test_connector, so an agent cannot tell which execution entry point applies to which object type.

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?

There is no guidance on when to use this versus tealfabric_execute_process or tealfabric_test_connector. The parenthetical '(optionally async)' hints at a choice, but it is not framed as a decision rule for the caller.

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