check_auth

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

Discloses key behaviors: navigates with QA_MCP_STORAGE_STATE session, checks for login-looking path, reports result. With no annotations, the description fully informs about nondestructive diagnostic nature.

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?

Two sentences, front-loaded with 'Diagnostic', no wasted words. Every sentence adds essential information.

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 simplicity of the tool, the description covers all needed aspects: function, when to use, and behavioral traits. No missing details.

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 covers both parameters comprehensively (100%). The description adds context about session usage and the purpose of the URL parameter, providing incremental value beyond 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 clearly states the tool's function: it navigates with a session and checks for login page bounce. It distinguishes itself from sibling extraction tools by being a diagnostic for session 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 specifies use case: 'when extractions unexpectedly return login forms instead of the requested page.' No ambiguity about when to apply.

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