Get hosts using a credential

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

The description only restates the tool's basic behavior and adds nothing beyond the annotations already declaring readOnlyHint=true and destructiveHint=false. It does not disclose response behavior, empty-result handling, or any other behavioral nuance.

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 two sentences are redundant: 'Get hosts using a credential' and 'Retrieves a list of hosts that are using a specific credential' say essentially the same thing. The first sentence repeats the title without adding value.

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 is simple: one required parameter, read-only annotations, and no output schema. The description names the output as a list of hosts, which is minimally adequate for invocation, but it does not describe what host fields are returned or any edge-case behavior.

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 schema provides no description for the id parameter (0% coverage). The description's phrase 'using a specific credential' hints that id refers to a credential ID, but it never explicitly defines the parameter or its format. This falls short of compensating for the missing schema documentation.

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 uses a specific verb ('Retrieves a list of hosts') tied to a clear resource ('hosts that are using a specific credential') and is clearly distinct from credential-list and credential-detail tools. However, it does not explicitly contrast itself with sibling tools like get_all_credentials or get_specific_credential, so it stops short of full 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 about when to use this tool versus alternatives such as listing all credentials or fetching a specific credential. The intended use is implied by the title, but nothing is stated.

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