get_browser_auth_status

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

With no annotations, the description carries the full burden, and it does add one real safety fact: cookies and credentials are never returned. It still leaves the agent guessing whether the call is read-only in effect, what permissions or configuration it needs, and how the status is expressed, which matters for a browser-auth tool.

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?

A single front-loaded sentence with no filler; the security caveat is attached directly to the action and nothing is redundant.

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?

There is no output schema, so the description is the only place the return value could be characterized, and it never says whether status is a boolean, an enum, or per-provider detail. Combined with no annotations and no guidance relative to the login/logout siblings, it is adequate but leaves meaningful gaps.

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 description coverage is 0%, so the description must compensate; it partially does by framing 'provider' as an opt-in browser-auth provider rather than an arbitrary identifier. The enum (linkedin, naukri) is self-explanatory but the description adds no per-provider behavioral notes beyond the qualifier.

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?

Names a specific verb and resource ('Get ... browser authentication status') scoped to a provider, which is precise enough to act on. It does not, however, distinguish itself from closely related siblings like start_browser_login, complete_browser_login, or logout_browser_session.

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 phrase 'opt-in provider' implies this is a pre-check on a provider whose session the user has opted into, but there is no explicit statement of when to call it (e.g., before start_browser_login) or when to use a sibling instead. Usage must be inferred from the name and the surrounding login toolset.

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