Apply a credential to a host

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the agent knows this mutates state but is not destructive. The description adds nothing about side effects—e.g., whether it overwrites existing credentials, requires specific permissions, or affects host connectivity. It does not contradict annotations but fails to add meaningful behavioral context.

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 short but contains redundancy: 'Apply a credential to a host. Applies a credential to an SSH host...' The same idea is stated twice. It could be reduced to a single sentence without losing content, but it is not bloated with unnecessary detail. The structure is acceptable but not optimally 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?

For a mutation tool with no output schema, no parameter documentation, and no usage guidance, the description is insufficient. It does not explain the result of applying a credential, whether it is reversible, or how it relates to similar tools. Given the complexity of the credential/host domain, an agent would likely need more context to use this correctly.

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%—the schema has no descriptions for 'id' or 'hostId'. The description provides no explanation of what these parameters represent (e.g., credential ID and host ID). With two required parameters and zero documentation, the agent cannot infer their meaning from the description alone, making this a critical gap.

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 clear action (apply a credential) and a target (a host), so the core purpose is discernible. However, it is redundant ('Apply a credential to a host. Applies a credential to an SSH host...') and does not differentiate from similar sibling tools like deploy_ssh_key_host, which also attaches a credential to a host. It avoids tautology but adds little beyond the title.

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 guidance is given on when to use this tool versus alternatives. The phrase 'for quick application' is vague and does not clarify when this is preferred over deploy_ssh_key_host, create_new_credential, or other credential-management tools. No exclusions or conditions are stated.

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