Cancelled enrollments of a session

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavioral value beyond that: result ordering ('oldest enrollment first') and, critically, a prompt-injection warning that `free_text` is human-typed data to be quoted, never obeyed. It does not mention pagination or result-size limits, which keeps it below 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?

Two short blocks, purpose and ordering front-loaded, followed by a focused safety note. No redundant restatement of the title or schema, and every sentence carries information.

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 annotations and an output schema, the definition covers purpose, ordering, and the one non-obvious hazard (untrusted free-text). Only the absence of any statement about result volume or pagination keeps it from being fully complete.

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 description coverage is 100%, with the schema itself explaining that session_id comes from sessions_in_week. The description adds only the framing 'of one session', so the baseline of 3 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?

Names a specific verb and resource ('List the cancelled enrollments of one session') and enumerates the returned fields (trainee, cancellation date, reason) plus the ordering (oldest first). This clearly separates it from siblings such as session_detail (whole session) and cancel_enrollment (mutation).

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?

The scope statement implies when the tool applies (you have one session and want its cancellations), and the schema points to sessions_in_week as the source of the id. However, there is no explicit when-not guidance or routing advice versus session_detail, which also covers a session.

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