Get all credentials

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

The annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior Mendot. The description adds 'for the authenticated user', which clarifies data scope, but does not disclose other behavioral details. No contradiction with annotations.

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?

Two short sentences, with the first serving as a preview and the second adding the key scoping detail. Slight redundancy with the title, but overall efficient and appropriately sized.

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 zero-parameter read-only operation, this definition covers action, resource, scope, and outcome (retrieves all SSH credentials). No output schema exists, but the description communicates the expected result well enough.

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 has zero parameters and schema coverage is 100%, so there is nothing for the description to add about parameters. The description's reference to 'all SSH credentials' is sufficient for this zero-parameter list operation.

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?

Description uses a specific verb ('Get') and resource ('all SSH credentials'), explicitly scoped to 'the authenticated user'. The 'all' scope clearly distinguishes it from sibling termix_credentials_get_specific_credential.

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 states what it does but does not explicitly contrast with alternatives such as get_specific_credential or get_credential_folders. The appropriate usage is implied by the word 'all', but no when-not-to-use guidance is provided.

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