passgage_list_leave_rules

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

With no annotations provided, the description carries the full burden. It accurately indicates a read-only listing operation with optional filtering and pagination, but it does not disclose details such as response format, default sort order, or authentication requirements. The behavior is transparent at a basic level but not richly described.

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 a single, front-loaded sentence that communicates the essential action and two key modifiers. Every word earns its place, with no redundancy or filler.

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 list tool with a well-documented schema, the description is minimally sufficient. However, there is no output schema and no annotation coverage, so the description could have provided more context about what is returned, typical usage, or limits beyond the schema. It remains adequate but sparse.

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 already provides complete descriptions for all three parameters, including examples for filters and bounds for pagination. The description only generically mentions 'filtering and pagination' and adds no meaning beyond what the schema already provides, matching the baseline for high schema coverage.

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 action ('List') and the resource ('leave_rules'), and mentions optional filtering and pagination. It differentiates from sibling get/create/update/delete tools by indicating a list operation, though it doesn't elaborate on what leave_rules are or how this list differs from other list_* tools beyond the resource name.

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 implies usage when you need to list multiple leave_rules and mentions filtering/pagination, but it does not explicitly say when to use this tool instead of get_leave_rule or other alternatives. No exclusion criteria or alternative tools are named.

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