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

Since no annotations are present, the description must carry the behavioral burden. It explicitly discloses operational constraints, such as failure modes ('not-found' vs. 'lookup fails') and the conditional logic used internally ('hiring_manager' when confident vs 'referral' otherwise).

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 dense paragraph, but every sentence contributes to the functional specification and operational constraints. While dense, it is efficiently written without unnecessary 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?

The definition is highly complete for a tool without annotations, as it covers the logic of retrieval, the specific failure modes, and the conditions governing the returned value.

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?

Although the provided schema does not include a `slot` parameter, the description provides vital semantic meaning by defining the tool's core branching behavior based on this distinction. This context helps an agent understand the underlying logic and limitations of the function.

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 provides a clear and nuanced purpose: finding specific individuals (hiring manager or peer) to ask about a saved job application. It effectively defines the tool's goal beyond a simple retrieval function.

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?

It provides excellent usage guidance by defining the condition for choosing one contact type over another (confident vs. peer). It also includes critical operational guidance regarding expected failure modes and retry logic.

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