aws_refresh_if_expiring_soon

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

The description fully discloses the tool's behavior: it checks token expiry and may trigger aws_login_start if expiring. This matches annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false) and adds context about the threshold and return behavior.

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 with no wasted words. Each sentence serves a purpose: stating the tool's role, explaining the two outcomes, and providing usage guidance.

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?

Given the simple tool with 2 optional parameters and no output schema, the description covers purpose, usage, parameter defaults, and return behavior. It is complete for an AI agent to decide when and how to use it.

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. The description adds value by explaining the meaning of thresholdMinutes (default 10) and profile (defaults to AWS_PROFILE or 'default'), and how they affect the tool's behavior.

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 performs a proactive SSO token check and either refreshes the token or returns an OK status. It specifies the verb 'Proactive SSO token check' and distinguishes itself from sibling AWS tools by focusing on token expiration.

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?

Explicitly says 'Use at the start of a multi-step AWS workflow to avoid mid-session expiry', providing clear context for when to use. It does not explicitly mention when not to use, but the guidance is sufficient for an AI agent.

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