Updsts Get Credential Info List

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

With no annotations, the description carries the full burden. 'Get' implies a read, but it does not state permissions, whether it touches disk at the given path, or what happens when cred_file is empty beyond what the schema already says. Behavioral disclosure is minimal.

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 that largely restate each other ('Get ... credential information list' vs 'retrieves the all AWS credentials'), with typos ('registerd', 'the all'). The second sentence adds no information and should have been cut.

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 one-parameter read tool with an output schema, the definition is minimally sufficient: it names the resource and the source file. It leaves out any indication of auth requirements or failure modes, but the output schema covers the return shape.

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?

There is a single parameter and schema description coverage is 100%, so the schema already explains cred_file and the empty-string default. The description only restates that credentials come from cred_file, adding nothing new; baseline 3 applies.

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 states a specific verb and resource: retrieving registered AWS credential info for all profiles. It is distinguishable from the sibling updsts_get_credential_info (singular) by the 'list / all profiles' scope, though it never explicitly contrasts them.

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?

No guidance on when to use this versus updsts_get_credential_info or updsts_update_sts_credential. An agent must infer that the plural 'list' variant is for enumerating all entries; nothing in the text confirms or excludes that.

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