get_connect_restart

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

The description says 'Restart a connector,' which is a state-changing operation, while the annotations declare readOnlyHint=true and destructiveHint=false. This is a direct contradiction: a restart is not read-only. The description also provides no detail about what the restart does to the connector's runtime state.

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, efficient sentence with no filler words. It is not overly verbose, though it is slightly too terse to be considered excellent given the operational nature of the action.

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?

The description is far too minimal for a state-changing operation: it does not explain what 'restart' means here, what side effects occur, what response to expect, or when it should be used. The annotation contradiction also makes the overall context misleading rather than merely incomplete.

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 description coverage is 100%, with each parameter (name, cluster, connectId) having a basic description. The tool description adds no parameter meaning, but because the schema already documents all three parameters, the baseline score of 3 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 states a specific verb ('Restart') and resource ('a connector'), so an agent can tell it is an operational action rather than a retrieval. It is clear, though it does not explicitly differentiate from the sibling get_connect_task_restart, which restarts a connector task.

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 on when to use this tool versus alternatives such as get_connect_resume, get_connect_pause, or get_connect_task_restart. The description gives no context about prerequisites, side effects, or why an agent would choose this operation.

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