Save SSH Task

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

The description adds valuable behavioral context beyond the annotations: on update, omitted description and defaultConnectionId retain current values, null clears defaultConnectionId, and step types/configuration are validated by the SSH engine. This meaningfully explains side effects and update behavior. No contradiction with annotations exists.

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 three sentences, front-loaded with the core action, and every sentence carries useful information. No filler or repetition of schema details.

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 tool has create/update behavior, nested step objects, and several optional parameters, and the description captures the key update semantics and validation. However, the create/update identification mechanism (taskId) and step configuration contract remain underspecified, so the description is not fully complete for an agent needing to construct valid requests.

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 0%, so the description must compensate, but it only explains update behavior for description and defaultConnectionId and the validation of step types/config. It does not clarify how taskId identifies a task for update, the role of workspaceId, or the structure of configJson and step id/configVersion fields.

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 identifies the tool as creating or updating a saved SSH task, with a specific resource and action. The partial-update semantics and validation detail further distinguish it from sibling task operations like duplicate_task, delete_task, and reorder_tasks.

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 clear context for when to use this tool: creating or updating a saved SSH task. It does not explicitly mention alternatives or exclusion criteria, but the create/update framing is strong enough to guide selection among task-related siblings.

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