get_absences

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

With no annotations present, the description carries the full burden of behavioral disclosure. It implies a read-only operation, but it does not mention whether the tool is safe, whether it modifies anything, whether pagination is involved, or how it handles missing absence data.

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 one compact sentence with no filler, and the main resource is front-loaded. It is appropriately short, though the brevity sacrifices some needed detail that other dimensions are forced to penalize.

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 tool with no output schema, no annotations, and an undocumented parameter, the description is incomplete. It explains the basic purpose but omits the meaning of 'subdomain', how the absence records are scoped, and any behavioral or output details an agent would need to invoke it confidently.

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 a single 'subdomain' parameter with no description, and the tool description never mentions it. With 0% schema description coverage, the description needed to explain what subdomain means and why it is needed, but it does not.

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 a specific resource ('absence records') and a source ('timeline notifications'), so the purpose is reasonably clear. It does not, however, explicitly differentiate itself from sibling tools like get_notifications or get_notification_history.

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?

No guidance is given about when to use this tool versus alternatives, prerequisites, or authentication context. The description only states what it returns, which forces the agent to infer when it is the correct choice.

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