pilot_auth

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

With no annotations, description fully discloses behaviors: three actions, what is stored (cookies+localStorage+sessionStorage), return values per action, and two specific error conditions. No contradictions or omissions.

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?

Description is well-organized into paragraphs covering purpose, usage, parameters, returns, and errors. Every sentence adds value, though slightly verbose in listing return values. Front-loaded with core purpose.

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 complexity (three actions, file I/O, session state), description covers all necessary aspects: purpose, usage, parameters, returns, errors, and sibling differentiation. No output schema, but return values are described. Complete for agent invocation.

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. Description goes beyond schema by explaining the meaning of each action, when path is required, giving an example path, and detailing return values per action. Adds significant value.

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?

Description clearly states 'Save, load, or clear browser session state (cookies + localStorage + sessionStorage) to/from a JSON file.' Provides specific verb+resource and explicitly differentiates from sibling tool pilot_import_cookies.

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 describes when to use: 'when user wants to authenticate once and reuse credentials across sessions, skip re-login flows, or transfer session state between runs.' Also contrasts with sibling pilot_import_cookies, giving clear guidance on alternatives.

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