ssh_setup_credentials

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

No annotations are provided, so the description must carry the full behavioral disclosure burden. It does reveal that the tool uses interactive GUI prompts, which is valuable, but it says nothing about where credentials are stored, whether existing credentials are overwritten, whether the call blocks waiting for a human, or what permissions it needs.

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?

It is a single front-loaded sentence with no wasted words. The brevity borders on under-specification rather than true conciseness, but from a structural standpoint 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?

An output schema exists, so return values need not be explained, but for a credential-mutating, interactive tool with no annotations, the description omits critical facts for an agent: whether a human must be present to answer GUI prompts, whether the call blocks, and whether it affects stored state for other SSH tools. That is a significant gap for this complexity.

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% for the single required parameter, and the description never mentions hostname or its expected format such as a DNS name or user@host. The word 'host' offers only a faint hint, so the description does not compensate for the undocumented parameter.

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 gives a specific verb and resource, 'Setup credentials', scoped to a Linux host, and adds the useful detail that it works through GUI prompts. It does not distinguish itself from nearby tools such as cache_credentials or ssh_clear_credentials, which perform related credential operations, so it falls short of full sibling differentiation.

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 call this instead of cache_credentials, or of when to call it at all relative to ssh_execute_ssh and the other siblings. The agent must infer that this tool is a prerequisite for other SSH operations and that it supersedes other credential-caching options.

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