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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states what the tool does, not what happens on success/failure, required auth, or whether the referral is nested or standalone. For a retrieve operation, this is minimal transparency.

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, directly worded sentence with no filler. Every word contributes to meaning, making it both concise and front-loaded.

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 tool is simple (2 required parameters, no output schema, no annotations). The description covers the core purpose, and the schema covers parameters, but the agent receives no information about return format, error cases, or relationship to list_opportunity_referrals. This is adequate but leaves identifiable gaps.

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 description coverage is 100%, with both referral_id and opportunity_id described. The description adds no additional meaning beyond 'one referral form for an opportunity,' which matches the schema. Per the baseline rule, a 3 is appropriate since the schema already handles parameter documentation.

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 uses a specific verb 'Retrieve' and names the resource 'one Lever referral form' with the scope 'for an opportunity.' This clearly identifies the action and distinguishes it from sibling tools like list_opportunity_referrals, which retrieve multiple referrals.

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?

The description implies usage—'one' suggests this is for retrieving a single referral by ID—but it does not explicitly state when to choose this over list_opportunity_referrals or provide any exclusionary guidance. No alternatives are mentioned, so the usage context is only implied.

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