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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds useful behavior beyond that: the row grain, the status vocabulary, and that a reason is returned. It says nothing about ordering, pagination, or what 'so far' means temporally, despite a limit parameter existing.

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 dense sentences with essentially no filler; the row grain and status list come first, then the filtering guidance. The opening clause 'What a program has sent so far' is slightly loose but is immediately clarified by the following phrase.

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 usefully describes the returned rows and their status/reason fields, which is the most important missing piece. For a five-parameter filtered list tool, the remaining gap is pagination and limit behavior, which is a minor but real omission.

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 0%, so the description carries the burden, and it does: it explains that enrollmentId, programId, clientId and status are filters and gives meaning to the status values. The limit parameter is never mentioned and it is unclear whether filters combine or how many may be applied, leaving one of five parameters undocumented.

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 description names the resource (program occurrences) and defines the exact grain: 'one row per item per day per client, with status (DONE, FAILED, SKIPPED, PENDING) and the reason.' That is far more specific than the name alone. It stops short of explicitly distinguishing itself from close siblings such as list_program_enrollments or retry_program_occurrence, so it is clear but not sibling-differentiated.

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 gives a concrete usage trigger: filter by status FAILED 'shows what needs a retry,' which routes the agent toward the retry workflow. It also enumerates the valid filter dimensions. It does not say when to use this versus list_program_enrollments or get_program, so alternatives are only implied.

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