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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds genuinely non-obvious behavior: the call 'opens nothing by itself' and returns procedural guidance (screens, buttons, fields) instead of data. It also pre-empts an agent from reaching for the Bullhorn REST API. It stops short of describing the shape or length of the returned guide.

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 purpose and the 'opens nothing by itself' correction are front-loaded, which is good. The trailing sentence about Bullhorn's REST API being sold as a paid partner contract with a date stamp ('checked 23 Oct 2026') is defensive justification that does not help an agent select or invoke the tool, and it dilutes a definition that could be two sentences.

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?

With zero parameters, no output schema, and full annotation coverage, the description carries the remaining burden well: it tells the agent what comes back (a step-by-step guide) and what to do next. Only a slightly richer characterization of the returned guide would make it complete.

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 and the description correctly introduces none, so there is no parameter-semantics burden to carry. Baseline 4 applies since the schema is empty and additionalProperties=false already constrains invocation.

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 names a specific verb and resource ('Search candidates in the user's own Bullhorn account') and then clarifies that it really returns a step-by-step how-to rather than results. That reframing is essential and accurate. It does not, however, distinguish itself from the sibling 'bullhorn_find_matching_candidates_for_a_job', which sounds like a competing candidate-search entry point.

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?

Usage is implied rather than stated: the agent learns it should call this first to get instructions, then execute with 'cotlet_browser_* tools in the user's Bullhorn Cloud Browser'. That is a useful workflow hint, but there is no explicit when-not guidance and no routing between this tool and the other Bullhorn candidate-search sibling.

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