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

Annotations cover the safety profile (readOnlyHint, openWorldHint=false), and the description adds substantial domain behavior: one application per learner per course, reapplication reopens the same record as pending, applicant not enrolled until approved, and the applicationData shape including legacy flat objects. This is context far beyond what the annotations provide.

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?

Dense and front-loaded with the core purpose and the routing alternative first, then semantics, then return shape. It is long, but nearly every clause carries actionable information (reapplication semantics, output fields) that has no other home since there is no output schema.

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:[...]}), the nested applicationData variants, and the review/decision fields, plus enum semantics for status. Nothing an agent needs to call or interpret this tool correctly appears 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, but the description adds meaning beyond the schema by framing status:"pending" as the review queue and courseId as selecting a single course's queue. It does not add format/syntax details for limit/offset beyond what the schema already states.

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 requiring approval) with qualifying scope (newest first, includes applicant and answers). It explicitly names the sibling enrollment_list as the alternative for enrolled/waitlisted learners, so an agent can distinguish it without opening a 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 when-to-use guidance: status:"pending" is the review queue, add courseId for a single course's queue, and use enrollment_list otherwise. It also tells the agent the follow-up action (approve/reject via application_review with the id).

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