topics_create_credentials

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

Discloses that secret_key is shown only once and that resources are not taggable. Lacks details on auth requirements, rate limits, or error states. With no annotations, the description carries burden but covers key behavioral traits.

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 sentences plus a parenthetical note. Each sentence is meaningful: purpose, critical usage instruction, and rationale for tagging behavior. No wasted words, front-loaded.

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?

Covers the essential one-time secret behavior and environment variable setup for data-plane tools. Benefits from existing output schema. Missing error handling or dependency notes, but sufficient for a create 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 baseline is 3. Description does not add meaning beyond parameter names and defaults. No elaboration on how parameters affect functionality.

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 the action 'Create SNS credentials for the data plane.' It distinguishes from sibling tools like queues_create_credentials by specifying SNS and data plane 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?

Provides explicit instructions on handling the returned secret_key (capture now, set env vars) and explains why resources are not tagged. Does not explicitly contrast with alternatives like queues_create_credentials but gives strong usage context.

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