Auto-Browser

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It successfully lists what data is accessed (the five profile fields), implying a read-only operation, but fails to disclose side effects, authentication requirements, or what happens when extraction fails (e.g., returns null vs throws error).

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 a single, efficient sentence that front-loads the verb. However, it is overly terse given the lack of schema documentation—it should sacrifice some conciseness to document the required parameter or extraction failure modes.

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 absence of an output schema, the description partially compensates by enumerating the extracted fields. However, with zero schema coverage on the input side and no annotations, the description is incomplete—it omits critical context about the session_id parameter and return behavior when not on a profile page.

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 input schema has 0% description coverage for the required 'session_id' parameter, and the description fails to compensate by explaining what session_id represents, its format, or how it relates to the 'current page' mentioned in the description. The agent receives no guidance on how to obtain or format this parameter.

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 specific action ('Extract'), resource ('profile info'), and exact fields returned (username, bio, followers, following, avatar). It effectively distinguishes from sibling tool 'social.extract_posts' by specifying profile metadata versus posts, and from 'browser.get_html' by emphasizing structured data extraction rather than raw HTML.

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 'from the current page' implies the tool operates on the active browser session, providing implicit context. However, it lacks explicit guidance on when to use this versus 'social.search' or prerequisites like 'must be on a profile page,' and does not mention error handling if the current page isn't a valid profile.

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