Updsts Get Credential Info

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

With no annotations provided, the description carries the full behavioral burden. It does disclose the data source (the AWS credentials file) and that results are per-profile, but it does not state that this is a read-only operation returning sensitive secret material, nor what happens when the profile is absent or file unreadable.

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 second sentence restates the first almost verbatim, adding no new information, and both instances of 'registerd' are misspelled. The core statement is front-loaded but roughly half the text is redundant.

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?

Return values need not be explained since an output schema exists, and both parameters are schema-documented. However, the description omits the routing guidance and existence/permission caveats an agent would need for a credentials-reading tool with two siblings.

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 both `cred_file` (default-file fallback) and `profile_name` are already documented by the schema. The description only echoes the profile-name concept and adds no format, encoding, or path-syntax detail beyond the schema.

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 names a specific verb (Get/retrieves) and resource (AWS credential information) scoped to a profile name, so the agent knows exactly what it returns. It does not explicitly distinguish itself from the sibling `updsts_get_credential_info_list`, though 'for the specified profile' implicitly signals single-profile scope.

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 on when to use this versus `updsts_get_credential_info_list` or `updsts_update_sts_credential`, and no preconditions (e.g., profile must already exist in the credentials file). The agent must infer usage from the name alone.

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