get_connect_pause

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

The description says 'Pause a connector,' which implies a state-changing operation, but the annotations mark readOnlyHint as true. This is a direct annotation contradiction. The description also does not disclose what pausing does to the connector state, whether it is reversible, or what the outcome 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 four-word description is extremely concise and front-loaded, with no filler or redundant phrasing. It could include slightly more behavioral context while still remaining concise, but as written it is efficient.

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?

With no output schema and an annotation contradiction, the description leaves important gaps: the effect on the connector, how the three required identifiers relate to the pause operation, and what response is expected are all unstated. The conflicting read-only annotation makes the context actively misleading.

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 describes all three parameters (name, cluster, connectId) with 100% coverage, so the description does not need to repeat them. It adds no additional meaning beyond what the schema provides, which meets the baseline for well-covered schemas.

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 action ('Pause') and a clear target ('a connector'), so the tool's basic function is understandable. It is not a tautology and is distinguishable from sibling tools like get_connect_resume and get_connect_restart, though it does not add any scope or contextual nuance.

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 description gives no guidance about when to use this tool, what conditions apply, or how it compares to alternatives such as resume or restart. The agent is left to infer when pausing is appropriate.

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