get_credentials_for_service

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

No annotations are provided, so the description must fully disclose behavior. It only states the basic read operation. It does not mention that passwords are excluded by default (only deducible from schema), what happens when the service does not exist, or if the operation has side effects. For a safe read operation, this is minimally acceptable but lacks depth.

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 a single sentence with no unnecessary words. It is front-loaded with the essential information and no filler. Every part contributes to the purpose.

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 description is minimal and covers the basic purpose, but given the lack of output schema and the presence of multiple sibling credential tools, more context would be helpful. It does not describe the return format, error scenarios, or behavior when service is unknown. Adequate for a simple read tool but not comprehensive.

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 100%, so the baseline is 3. The description adds no additional meaning beyond the schema's parameter descriptions. It mentions 'including passwords' but that directly mirrors the parameter description. No new context or constraints are provided.

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 specifies the action ('Get all credentials'), the target resource ('credentials'), and the filtering criterion ('for a specific service'). It distinguishes itself from sibling tools like 'get_credentials' which likely returns all credentials, and 'list_credentials' which may return metadata only.

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 provides no guidance on when to use this tool over alternatives (e.g., 'get_credentials', 'list_credentials'). It does not state when to avoid it or mention prerequisites like having a service already configured. The usage context is only implied by the tool name.

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