list_time_off_balances_by_policy

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

No annotations are provided, and the description only mentions pagination. It does not disclose behavioral traits such as authentication needs, rate limits, error handling, or what happens when the policy does not exist.

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 short sentence, which is concise but too brief. It front-loads the action but omits essential detail. Every word is meaningful, but more context would not harm conciseness.

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 6 parameters (1 required), no output schema, and no annotations, the description fails to provide sufficient context. Pagination and sorting are mentioned implicitly but not fully explained, and return values are omitted.

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 description has 0% schema coverage and does not explain any of the six parameters (policy_id, workspace_id, sort, sort_order, page, page_size). The agent gets no help on how to populate these fields beyond their types and names.

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 verb 'List', the resource 'per-user time-off balances', and the scope 'for a policy' with 'paginated' hint. It distinguishes from sibling list_time_off_balances_by_user by specifying policy-level granularity.

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 does not explicitly state when to use this tool versus alternatives like list_time_off_balances_by_user. Usage is implied by the tool name, but no guidance on when-not-to-use or context is provided.

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