open

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

With no annotations, the definition must carry the full behavioral burden. It does disclose one useful trait (headed opens a local window, implying a visible browser process), but says nothing about side effects, whether a profile is created if absent, what "check login" returns or throws, or whether the operation is synchronous or blocking. For a launch-style tool this is a significant disclosure 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?

A single compact sentence with the core action front-loaded and the window behavior appended as a clarifying clause. Nothing is padded, though the compression contributes to the under-specification noted elsewhere.

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 and no annotations, so the description is the only source of behavioral detail, yet it omits return values, error conditions, and three of four parameter meanings. For a tool that launches something and authenticates, an agent is left guessing at critical details.

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% across four parameters, and the definition only explains one of them (headed). The required 'profile' parameter is never clarified (name? id? path?), and 'site' and 'note' receive no mention at all, leaving half the inputs undocumented in both schema and description.

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 definition names a verb (start) and an object (a profile) plus a secondary check-login action, which gives a rough sense of what happens. However, "profile" is never defined and the framing is abstract, so an agent cannot fully tell whether this launches a browser session, provisions an account, or something else. It is enough to distinguish it from list_profiles or close, but only barely.

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 "on demand" hints at a triggering context but never states when this should be called versus siblings such as list_profiles, exec, or close. No preconditions, no alternatives, no exclusions are given, leaving the agent to infer usage from the tool name alone.

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