zendesk_wfm_get_activities

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

Discloses record limit (1000), pagination method (using startTime of last activity), and authentication requirements. No annotations are provided, so the description adequately covers behavioral expectations.

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?

Three sentences, each serving a distinct purpose: action, limits, pagination, and authentication. No redundant or missing information.

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?

Sufficient for a simple tool with one parameter and no output schema. Covers purpose, pagination, and auth. Could mention error handling but not required for basic usage.

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?

Adds meaningful context beyond the schema by explaining how startTime is used for pagination. Schema coverage is 100%, so baseline 3; the pagination guidance raises it to 4.

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 activities starting from a Unix timestamp, with pagination details. It distinguishes from sibling tools that deal with shifts, reports, or time off.

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?

Includes pagination instructions and required authentication tokens. Does not explicitly state when to use this tool versus alternatives, but the scope of activities is implied.

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