queues_create_credentials

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

No annotations are provided, so the description carries the full burden. It discloses that the returned secret_key is shown only once and that credentials are not tagged as managed. It does not mention required permissions or side effects, but the one-time display is a critical behavioral trait well communicated.

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 three sentences, front-loaded with the main purpose. Every sentence provides useful information with no redundancy or fluff. It is efficient and well-structured.

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 has an output schema, and the description explains the key aspects of the return (secret_key shown once, access_key) and how to use them. It does not cover credential management beyond creation, but given the sibling tool queues_list_credentials, this is acceptable. The description is mostly complete for a credential creation tool.

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 100%, so the schema already documents all parameters well. The description adds minimal extra semantic value, mentioning the returned keys but not elaborating on any parameter beyond the schema. A score of 3 is appropriate as the description does not significantly enhance parameter understanding.

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 states it creates SQS credentials for the data plane, specifying the resource and action. However, it does not differentiate from sibling tools like topics_create_credentials, which could cause confusion without additional context.

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 tells when to use the tool: to obtain credentials for the data plane. It provides important instructions to capture the secret_key immediately and set environment variables for data-plane tools. It mentions that MnQ resources are not taggable. Lacks explicit when-not-to-use or alternatives.

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