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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description still adds the membership/authorization requirement plus the concrete shape of returned data including stored voicemail, summary, and transcript. It omits any volume, pagination, or ordering behavior, which keeps 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?

The resource is front-loaded, but the core sentence is a long run-on that packs the entire return payload into one clause chain. The field inventory earns its place; the phrasing could be broken up or compressed without losing meaning.

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 no output schema, the description must carry return-value explanation, and it does so reasonably by listing the record types returned. However, for a two-action dispatch tool the action semantics are the critical missing piece, so an agent still cannot confidently invoke activity versus contact_card without a help round-trip.

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 only 50% (the nested params object is undocumented beyond a pointer to "help"), so the description needs to compensate and does not. It names actions activity and contact_card without saying what either returns or when to choose one, leaving the agent dependent on a second help call to understand the primary dispatch 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?

The description names a specific resource (the member's own recruiter line) and enumerates what it exposes: inbound calls/texts, outbound calls, counterpart identity, timing, answer disposition, duration, and stored voicemail/summary/transcript. The read verb is only implicit (carried by the title 'Read the recruiter line'), and nothing distinguishes it from siblings like manage_line or call_line.

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 states a hard prerequisite (an Applystead membership) and points to action "help" for field details, which is real usage context. But it never says when to pick this over manage_line or call_line, and there are no exclusions or alternative routing.

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