zendesk_wfm_get_time_off

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

No annotations are present, so the description must communicate behavior. It mentions the requirement of an API token but does not disclose pagination, result limits, sorting, or response structure. The presence of page/pageSize parameters in the schema is not explained.

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 two sentences with no extraneous information. It front-loads the core purpose and adds a necessary authentication note concisely.

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?

The description is brief and covers the basic functionality but lacks details on output format, pagination behavior, and any prerequisites beyond the token. Given the tool's complexity (8 optional params, no output schema), more context would improve completeness.

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 covers all parameters with descriptions, so the description adds minimal value beyond listing filter categories. With 100% schema coverage, a baseline of 3 is appropriate.

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 tool retrieves WFM time off requests and lists the filter types. However, it does not differentiate from the sibling tool zendesk_wfm_get_time_off_v2, which likely has a similar purpose.

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 indicates optional filters but provides no guidance on when to use this tool versus alternatives, such as the v2 version. It does not specify scenarios where this tool is preferred or when not to use it.

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