check_amazon_auth_status

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes what the tool does (checks authentication status), what it returns (status, URL, error messages), and its purpose in a workflow (verification before other tools). However, it lacks details on potential side effects, rate limits, or specific error handling beyond mentioning 'error messages'.

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 description is front-loaded with the core purpose in the first sentence, followed by usage guidelines. Both sentences are essential—the first explains what the tool does, and the second explains when to use it—with zero wasted words or redundancy.

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 tool's low complexity (one parameter, no output schema, no annotations), the description is mostly complete. It covers purpose, usage, and output details. However, it could be more complete by specifying the exact format of the return values (e.g., structured data types) or any prerequisites, though this is mitigated by the simple context.

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 the schema fully documents the single parameter 'region' with its enum values. The description adds no additional parameter semantics beyond what the schema provides, such as explaining why region matters for authentication or how it affects the check. This meets the baseline for high schema coverage.

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 the specific action ('Check if the browser session is authenticated'), the resource ('Amazon for a specific region'), and the output ('authentication status, current URL, and any error messages'). It distinguishes this tool from its siblings, which are all data export or retrieval tools, by focusing on authentication verification rather than data extraction.

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 states when to use this tool ('to verify login status before running other tools') and when not to use it ('or to prompt user to log in if session expired'), providing clear context for its application. It implies alternatives by suggesting it should precede other tools, though it doesn't name specific alternatives.

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