zendesk_wfm_get_time_off_v2

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

No annotations are present, so the description must fully disclose behavioral traits. It only names the action ('Get') and a requirement, but fails to mention rate limits, pagination behavior, or the effect of omitting filters. The agent is left guessing about idempotency and safety.

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, front-loading the action and version. Every word serves a purpose; no fluff. Ideal conciseness for quick comprehension.

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?

With 8 optional parameters, no output schema, and no annotations, the description is very sparse. It doesn't explain filter combination semantics, default behavior (e.g., returns all if no filters), or what 'enhanced response fields' are. This leaves the agent underinformed for effective use.

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 baseline is 3. The description adds minimal value beyond the schema—'with optional filters' is generic. Parameter descriptions in schema are sufficient, but no extra context like date format specifics or valid enum values is provided.

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 it retrieves time-off requests using the v2 API, specifying it's an enhanced version. This distinguishes it from sibling tools like zendesk_wfm_get_time_off (original) and zendesk_wfm_import_time_off_v2 (import action).

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 mentions a requirement (ZENDESK_WFM_API_TOKEN) but provides no guidance on when to use this tool versus alternatives like the non-v2 version. The phrase 'Enhanced version' implies a preference but lacks explicit when/when-not criteria.

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