save_auth_profile

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It states the return dict but does not mention side effects, persistence location, overwrite behavior, or required permissions. For a save operation, this is a notable gap.

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 well-structured with an Args block and a Returns line, front-loading the core purpose. Every line earns its place by adding parameter semantics or clarifying expected output without 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?

For an 8-parameter tool with no annotations and no output schema, the description supplies strong invocation guidance: all parameters, defaults, conditional requirements, and return keys. It falls short only on side effects and tool-selection context, but is largely sufficient.

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, yet the description compensates thoroughly by explaining every parameter, its purpose, default values, and conditional requirements. It adds meaningful context such as 'user_data_dir helps with anti-bot OAuth' that the schema alone cannot convey.

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 saves an authentication profile for use in test runs, with a specific verb and resource. It does not explicitly distinguish itself from sibling tools like capture_auth_session, so it misses the top score.

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 provides conditional usage details such as login_url being required for env_login and default environment variable names. However, it never explicitly says when to use save_auth_profile versus alternatives like capture_auth_session, so usage guidance is only implied.

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