list_absences

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that absences are recorded, but does not mention whether the operation is read-only, requires specific permissions, or what the output format is (though an output schema exists). The lack of behavioral context is a significant gap.

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 description is extremely concise at nine words, but this brevity sacrifices necessary detail. It could be slightly longer to include a verb and scope without becoming verbose, so it is under-specified rather than efficiently concise.

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?

Given the tool has an output schema, the description is not required to detail return values. However, it lacks context about the nature of absences (e.g., dates, types) and any potential filtering. It is minimally complete for a simple list endpoint but leaves room for improvement.

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?

The input schema has 0% description coverage, so the description must compensate. The only parameter 'enrollment_id' is self-explanatory from its name, but the description does not clarify its format, source, or usage. Adding no value beyond the schema earns a low score.

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 'Absences recorded for one enrollment' clearly indicates that the tool returns absence records for a specific enrollment. It effectively communicates the resource (absences) and scope (one enrollment). It distinguishes from the sibling 'absence_summary' which likely provides aggregated data.

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 description offers no guidance on when to use this tool versus alternatives like 'absence_summary' or other sibling tools. It does not specify scenarios, prerequisites, or exclusions, leaving the agent to infer usage context.

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