Auto-Browser

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

No annotations are provided, so the description carries full burden but provides minimal behavioral disclosure. While 'Inspect' implies read-only, it doesn't explicitly confirm safety, describe error conditions (e.g., if profile_name doesn't exist), or explain the return format.

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 of 9 words is appropriately front-loaded with the action verb 'Inspect'. However, given the lack of annotations and schema coverage, this brevity leaves critical gaps rather than being efficiently informative.

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 zero annotations, no output schema, and 0% parameter coverage, the description is insufficient. It doesn't explain what 'storage-state metadata' contains, expected return structure, or prerequisites for successful 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?

With 0% schema description coverage, the description fails to compensate adequately. It mentions 'one saved auth profile' implying identification is needed, but doesn't explain the profile_name parameter, valid values, or that it should correspond to names returned by list_auth_profiles.

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 uses specific verb 'Inspect' with clear resource 'saved auth profile' and distinguishes from sibling 'list_auth_profiles' by emphasizing 'one' (single item retrieval vs. listing). It also differentiates from 'save_auth_profile' through the read-only verb choice.

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?

No guidance provided on when to use this tool versus alternatives. It fails to mention that users should typically call 'list_auth_profiles' first to obtain valid profile_name values, or clarify the relationship to 'save_auth_profile'.

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