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

Beyond the readOnlyHint annotation, the description explains pipeline state semantics, the advisory nature of suggestedStatus versus the reviewed approvedStatus, when screeningAnswers is empty, and how pagination and counts/total can disagree. These are meaningful behavioral traits that an agent would not get from the annotations or schema alone.

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 front-loaded with the core purpose and every sentence contributes useful semantics about statuses, output fields, pagination, or filtering. It is dense and slightly long for a list tool, but the length is largely justified by the absence of an output schema and the complexity of the applicant pipeline.

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?

For a paginated list tool with no output schema, the description covers the key return semantics: matchId, suggestedStatus, approvedStatus, screeningAnswers emptiness, pagination behavior, and the intentional difference between counts and total. It also names the relevant overview alternative, leaving little an agent would need to infer before calling it correctly.

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 already 100%, so the baseline is 3, but the description adds real meaning about the status enum by explaining which states are undecided, changeable manager decisions, or final. It also clarifies how offset is used when total exceeds the returned applicant count, though it does not add much beyond the schema for productId and limit.

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 first sentence states a specific verb and resource: list people who applied to this beta project through its screening form, including their answers. It explicitly distinguishes this tool from getApplicantsOverview and ties the returned matchId to reviewApplicants and inviteApplicants, so an agent can identify its role among siblings.

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 explicitly says to use getApplicantsOverview when only per-status counts are needed, which gives a clear alternative and implies this tool is for per-applicant detail. It also explains the pagination follow-up behavior and how the status filter interacts with total versus counts, giving practical invocation guidance.

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