List days-off requests

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

The description adds behavioral details beyond annotations: pagination behavior ('30 per page, zero-indexed pagination') and required scope. Annotations already indicate read-only and non-destructive, so the description complements well.

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 three short sentences, efficiently conveying key information without redundancy. It is front-loaded with the main purpose.

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 simple listing tool with no output schema, the description covers pagination and scope. It does not explain the response structure (e.g., items array, total count), but annotations (openWorldHint) and sibling tools provide some context. Still, a slightly more complete description of the response could be beneficial.

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 schema fully describes parameters. The description reiterates pagination info already in the schema parameter descriptions, adding no new semantic meaning.

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 clearly states the resource ('Calendar days off requests') and the action (list), with specific details like pagination. It distinguishes from sibling tools by focusing on days-off requests specifically.

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 provides helpful usage guidance by specifying the required scope ('calendar:read') and read-only nature. However, it does not explicitly state when to use this tool versus alternatives like officient_get_day_calendar or officient_get_month_calendar.

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