tealfabric_get_connector_oauth2_required

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

No annotations are provided, so the description carries the full behavioral burden. It implies a non-mutating check via 'Check whether', but does not state what happens if the connector_id is unknown/invalid, or what the answer looks like (boolean field name). For a trivial read-only predicate this is acceptable but not rich.

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?

One front-loaded sentence with zero filler; every word contributes to identifying the operation.

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 one-parameter boolean-style query with no output schema, the description conveys enough to invoke correctly. The remaining gap is that it does not explicitly describe the return value (a boolean flag), which would matter since no output schema exists.

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?

There is a single parameter with 100% schema coverage, so the schema already documents connector_id. The description adds no extra semantics such as accepted ID formats or where to obtain a connector_id (e.g., from tealfabric_list_connectors), so baseline 3 applies.

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 ('Check whether') plus a precise resource ('a connector requires OAuth2 authentication'), which is unambiguous about the operation. It does not name or differentiate from siblings such as tealfabric_test_connector, which sits closest to it in purpose.

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 predicate phrasing implies a pre-flight check (e.g., before configuring or testing a connector's auth), but the description never states when to call it, when not to, or how it relates to tealfabric_test_connector or the integration tools. Usage is only inferable.

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