tealfabric_get_connector_oauth2_required

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

With no annotations, the description carries the behavioral burden. 'Check whether' strongly implies a read-only predicate with no mutations, which is helpful. However, it does not disclose whether the check invokes external connector metadata, how failures are reported, or what the exact response shape is.

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, front-loaded sentence with no wasted words. It states the subject, the action, and the condition being checked efficiently.

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 simple single-parameter predicate, the description is nearly complete: an agent can infer the likely boolean result from 'whether.' It does not describe exact return values or error behavior, but the low complexity and full schema coverage make that omission minor.

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 schema already fully documents connector_id as a string with description 'Connector ID' and 100% coverage. The description adds no extra semantic detail about the parameter, so the 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 clearly states the purpose: checking whether a connector requires OAuth2 authentication, with a specific verb and resource. It does not explicitly distinguish itself from tealfabric_list_connectors or tealfabric_test_connector, but its intent is unmistakable.

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?

No guidance is provided about when to use this tool versus alternatives such as tealfabric_test_connector or tealfabric_list_connectors. The description implies a simple conditional check but does not state eligibility, context, or exclusions.

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