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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the tool produces instructions only, 'opens nothing by itself', and action must be carried out by separate browser tools. It doesn't describe the shape or length of the returned guide, which keeps it below 5.

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-loads the purpose and the instruction-only nature, then the handoff to browser tools, then supporting rationale about the API. The API paragraph is somewhat long for what it contributes, but it preempts a plausible wrong assumption and is therefore not waste. Three sentences, no filler.

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 zero-parameter, no-output-schema planning tool, the description covers what it returns (screens, buttons, fields), what it does not do (open anything), and what to call next. The remaining gap is that it doesn't state prerequisites such as an active Bullhorn Cloud Browser session or login state, which an agent would want before invoking it.

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 takes zero parameters, so there is no argument semantics for the description to explain and the baseline of 4 applies. Nothing in the description conflicts with the empty schema.

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?

States a specific verb and resource (list job submissions) and immediately discloses that the tool returns a step-by-step how-to rather than the data itself, which is the decisive fact an agent needs. It also routes to the cotlet_browser_* family rather than claiming to do the browsing. Minor deduction because the opening 'List job submissions' phrasing momentarily implies a data-returning tool before the second sentence corrects it.

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?

Gives a clear workflow: call this to get the procedure, then execute with cotlet_browser_* in the Bullhorn Cloud Browser. It also explains why the official Bullhorn REST API is not an option, which answers the obvious 'why not just use the API' question. It does not name a specific sibling alternative or state when this tool should not be used (e.g., when the user is not authenticated into Bullhorn), so it stops short of a 5.

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