Auto-Browser

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

With no annotations provided, the description carries full burden but fails to disclose critical behavioral traits: whether saving overwrites existing profiles, what exactly constitutes 'session storage' (cookies, localStorage, etc.), or potential error conditions.

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?

Single sentence, front-loaded with the action verb, zero redundant words. Every word earns its place by conveying the operation, source, and destination.

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?

Adequate for basic identification but incomplete given the tool's persistence nature and lack of supporting metadata (annotations/output schema). Should specify overwrite behavior and persistence scope to reach full completeness.

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?

The schema has 0% description coverage. The description partially compensates by implying 'profile_name' is the identifier ('named auth profile') and 'session_id' references the current session, but lacks explicit parameter mapping or format constraints (e.g., maxLength 120 is only in 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 provides a specific verb ('Save'), clear resource ('session storage state'), and distinct output ('reusable named auth profile'), clearly distinguishing this persistence operation from sibling retrieval tools like get_auth_profile or list_auth_profiles.

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 implies usage context ('reusable') suggesting when to persist auth state, but lacks explicit guidance on when to use this versus alternatives like forking sessions, and omits prerequisites like requiring an active session first.

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