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

With no annotations, the description carries the full burden and does well: it discloses the confidence-based selection logic, a not-found failure mode, and retry advice on transient lookup failure. It omits auth/permission requirements and what a successful response contains, keeping it from a 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?

Two tight sentences, front-loaded with the tool's core purpose before the failure/retry caveats. Dense but every clause is relevant, though the ambiguous 'slot' clause adds confusion rather than value.

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?

Covers failure modes and retry behavior for a small two-parameter tool, which is meaningful given no output schema or annotations. However, it never explains what contact information is returned or what 'limit' governs, and the phantom 'slot' parameter leaves the contract unclear.

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 100%, so jobId and limit are already documented, and the description adds nothing about limit. Worse, it references a 'slot' argument ('hiring_manager' or 'referral') that does not exist in the input schema, which can mislead an agent into passing an unsupported parameter.

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: find referrers (who to ask) for a given job, with a clear hiring-manager-vs-peer distinction. It does not differentiate from close siblings like get_job_recruiters or get_application_referrers, so it stops short of a 5.

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 through the hiring-manager/peer fallback logic and a retry hint on lookup failure, but there is no explicit guidance on when to prefer this tool over the sibling recruiter/referrer tools. The agent must infer selection from names alone.

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