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

Annotations only declare readOnlyHint=true; the description goes well beyond that by explaining the semantics of the two independent flags (active vs published), how pending aggregates new+needsReview, and that screeningSetUp=false is returned for betas without a form. With no output schema present, this return-shape disclosure carries real behavioral weight.

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 first sentence front-loads the purpose and the detail sentences each convey distinct facts (flag independence, pending bundling, screeningSetUp=false). It is slightly dense but no sentence is pure filler; the final sentence is the closest to redundant with the earlier 'returns whether a screening form is set up'.

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 single-parameter read tool with no output schema, the definition supplies the return contents, the meaning of each flag, the caveat about pending, and the empty-state behavior. There is nothing material an agent would need before invoking it.

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?

There is only one parameter and schema coverage is 100%; the schema already tells the agent to get valid IDs from listProducts. The description adds no additional meaning about productId, so the baseline 3 for a fully documented schema is appropriate.

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: a summary of a beta's applicant screening pipeline. It then enumerates exactly what the summary contains (form-setup flag, counts by stage, auto-suggestion rule count), which lets an agent distinguish it from listApplicants (individual records) and getScreeningSetup (form configuration) without opening schemas.

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?

Defines what an applicant is (filled out public screening form, no sign-in, reviewed then invited) and clarifies the relationship to listApplicants, explicitly noting that pending is not a valid listApplicants status filter. It never states a clean when-to-use-this-vs-sibling rule (e.g. 'use this for aggregate counts, use listApplicants for per-applicant data'), but the surrounding context makes the selection clear.

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