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

Annotations already declare readOnly/destructive=false, and the description layers on non-obvious domain behavior: an applicant is not enrolled until approved, one application per learner per course, and a rejected learner reapplying reopens the same application as pending with new answers. That lifecycle detail materially affects how an agent interprets 'pending' rows.

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?

Front-loaded with purpose, then routing, then data shape; every clause carries information. It is dense and runs long with stacked semicolons, and the full return-object enumeration is heavy, though defensible since no output schema exists.

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 supplies the return envelope ({total, count, applications:[...]}) and field list, plus the applicationData shape variants. Nothing an agent needs to call or interpret this list tool is missing.

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 the baseline is 3; the description adds semantics the schema lacks, framing status:'pending' as the review queue and courseId as scoping to one course's queue. Limit/offset paging semantics are left entirely to the schema, so it stops short of a 5.

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 ('List applications to courses that require applying before enrollment'), plus ordering ('newest first') and payload scope ('each with the applicant and their answers'). It explicitly contrasts itself with the sibling enrollment_list, so an agent can pick between them without opening either schema.

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?

Gives explicit routing: use enrollment_list for enrolled or waitlisted learners, status:'pending' is the review queue, add courseId for a single course's queue, and application_review handles decisions by id. Both when-to-use and when-to-use-something-else are stated.

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