list_connectors

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

There are no annotations, so the description carries the full burden of behavioral disclosure. 'List' implies a read operation, but the description does not mention authentication, environment semantics, pagination, rate limits, or what 'live' and 'curated' mean operationally. Minimal context beyond the action itself.

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 filler or repetition. Every word contributes meaning.

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 list tool with one optional boolean and no output schema, the description is minimally adequate: it names the resource, scope, approximate scale, and the one parametter. However, it does not clarify return shape, environment handling, or how it differs from list_connections, which is a notable gap given siblings.

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 0%, so the description must compensate for the undocumented 'curated' boolean parametter. The phrase '(or curated catalog)' provides a useful hint that the parametter toggles between the full environment list and a curated catalog, but it does not state explicit values or default behavior.

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 states a specific verb ('List') and resource ('connectors'), and clarifies scope: 1000+ live connectors in the environment or a curated catalog. It is distinguishable from sibling list_connections because it targets connectors rather than connections, though it does not explicitly name the sibling.

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 explicit guidance is given about when to choose this tool over siblings like list_connections, ensure_connection, or add_connector_action. The '(or curated catalog)' phrase hint at usage modes, but no alternatives or exclusion conditions are stated.

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