tealfabric_test_connector

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that it 'tests' a payload against an endpoint, but does not disclose whether the test is read-only, makes an external network call, or creates any temporary resources. This is a minimal statement rather than transparent behavioral documentation.

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 declarative sentence with no filler. The action and object are front-loaded, and every word contributes directly to understanding what the tool does.

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 one required parameter, no output schema, and no annotations, the description is functional but sparse: it does not tell the agent what result to expect, what a failed test looks like, or whether the test has side effects. For a low-complexity tool this is close to adequate, but there are clear gaps.

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 documents payload with 100% coverage as 'Connector configuration payload expected by the selected connector'. The description adds no new parameter-level detail beyond naming the endpoint, so the baseline of 3 for high schema coverage 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 opens with the clear verb 'Test' and names the exact resource ('connector configuration payload') and the specific endpoint ('Tealfabric connectors test endpoint'). It does not explicitly contrast with sibling tools like list_connectors or execute_process, but the action and object are specific enough that an agent can infer its distinct role.

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 about when to use this tool versus alternatives, such as validating a connector configuration before creating an integration, or any prerequisites like fetching the connector list first. The intended usage context must be inferred entirely from the tool name, which is minimal.

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