start_login

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

With no annotations, the description must carry the full burden of behavioral disclosure. It mentions the profile is 'persistent,' implying statefulness, but does not explain critical behaviors: whether it blocks on user interaction, what side effects occur (e.g., creating a profile, storing cookies), or what the call returns. This leaves significant behavioral uncertainty.

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, well-structured sentence that front-loads the verb and purpose. It contains no redundant or filler words, making it highly efficient.

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?

While the description clearly states the action, it omits crucial context such as the return value (despite an output schema existing), whether the call requires user interaction or waits, and how it fits into the broader login workflow with sibling tools. For a stateful, manual login process, this leaves too much unspecified.

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 tool has zero parameters, so schema coverage is trivially 100%. The description does not need to explain parameters, and the baseline for 0 params is 4. It adds no param-specific detail, but none is necessary.

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 is specific and action-oriented: 'Open a persistent Chromium profile' clearly states the action, and 'for a manual Agora Plus login' specifies the purpose. This differentiates it from sibling tools like portal_info or session_status, which likely inspect or query rather than initiate a login.

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 a clear context for use: it is for performing a manual Agora Plus login. However, it does not explicitly state when to use this tool versus alternatives (e.g., checking session_status first) or mention any prerequisites or exclusions.

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