aws_refresh_if_expiring_soon

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

The description discloses behavior beyond annotations: it can trigger aws_login_start, returns specific outputs (verification URL/code or status with minutes left), and mentions a default threshold of 10 minutes. Annotations only indicate non-readonly and non-destructive, so description adds significant value.

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?

Three sentences, each essential: purpose, conditional behavior, usage recommendation. No redundant information. Well-structured with clear cause-effect.

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?

No output schema exists, but the description explains the two possible return states (verification URL+code or status+minutes left). It doesn't detail exact structure of the verification response, but that can be inferred from aws_login_start sibling tool. Overall sufficient given tool simplicity.

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% with descriptions for both parameters. The description adds value by explaining the default thresholdMinutes (10) and the behavioral impact of crossing it, which the schema doesn't cover. This justifies a score above the baseline 3.

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's a proactive SSO token check, specifying two conditional behaviors: if expiring soon, it kicks off aws_login_start and returns verification URL/code; otherwise returns status 'ok'. This distinct verb+resource combination differentiates it from siblings like aws_login_start and aws_session_get.

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 explicitly advises using it 'at the start of a multi-step AWS workflow to avoid mid-session expiry', providing clear context. However, it doesn't mention alternatives or when not to use it, slightly limiting guidance.

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