bullhorn_session

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

With no annotations, the description carries the full burden and does it well: it explains the out-of-band browser/SSO/MFA flow, warns never to hand passwords or MFA codes to the assistant, and describes what each action yields. It omits session lifetime/expiry and what happens to existing sessions on login, which are the main remaining behavioral gaps.

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?

Front-loaded with the purpose, then structured Args/Returns sections; every line earns its place, including the security warning. The blank-line layout is slightly airy but not wasteful.

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 a two-parameter session tool with an output schema present, the description covers purpose, per-action semantics, the security constraint, and a brief return summary. An agent has everything needed to call it correctly without further context.

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 coverage is 0%, and the description fully compensates: it gives the default for action, lists all four allowed values, and explains that confirmation is the one-time code from the browser page and applies only to complete_link. That is more than the schema contains.

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 states a specific verb set and resource ('Show, start, complete or end your own Bullhorn sign-in for this workspace'), so the tool's job is unambiguous. It does not, however, name or contrast itself with plausible siblings like connection_status or setup_status, leaving the boundary to inference.

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?

Each action value is enumerated with its purpose (status default, login returns a link, complete_link finishes with the browser code, logout), which tells the agent exactly which mode to pick. It stops short of explicit when-not guidance or routing versus the sibling status tools.

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