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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds only the returned fields (Account/Arn); it does not say what happens when the profile is unauthenticated or expired (error vs. login prompt), which is the key behavioral question for an STS identity call.

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?

A single front-loaded sentence with the core purpose first and the optional input in parentheses; no filler. Only the slightly awkward parenthetical phrasing keeps it from being maximal.

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?

With annotations covering safety, a full schema and an output schema, the description is adequate but incomplete on the operationally important point: how this tool behaves with missing/invalid credentials and whether it interacts with the SSO login flow. For a two-parameter read tool that is a moderate gap rather than a fatal one.

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% for both parameters, so the schema carries parameter documentation. The description only restates that profile is optional and says nothing about context_id or what omitting profile falls back to (default/ambient credentials) — 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?

States a concrete verb and resource — 'Show the current identity (Account/Arn)' — plus the scoping input (profile). It is clearly distinguishable from the aws_sso_login_* siblings, which perform authentication rather than identity reporting, though it never names those siblings explicitly.

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 call this versus alternatives such as aws_sso_login or aws_sso_login_device_start, nor any stated precondition (e.g. 'call this to verify credentials before other aws_* tools'). The only usage hint is that profile is optional, which the schema already conveys.

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