List Work Activities

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds context about pagination and required company_id, but contains an internal inconsistency: it says it returns 'a paginated JSON array of Incidents' while the tool is about listing Work Activities, which may confuse agents.

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 reasonably concise with 5 sentences, each serving a purpose: purpose, usage, return type, required param, and API context. The endpoint detail is useful but could be integrated more succinctly.

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?

No output schema exists, so the description must convey return structure. It mentions 'paginated JSON array' and metadata, but doesn't specify fields of each item (e.g., Work Activity properties). The 'Incidents' reference is likely incorrect, reducing 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?

Schema coverage is 100% with parameter descriptions. The description adds value by explaining pagination usage ('Use page and per_page to control pagination') and response metadata, though it doesn't detail filter parameters beyond what the schema provides.

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 returns a list of Work Activities associated with a Company, with specific verb and resource. It differentiates from sibling tools by focusing on work activities and linking to incidents.

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 provides explicit usage guidance: 'Use this to enumerate Incidents when you need a paginated overview, to find IDs, or to filter by query parameters.' It also mentions pagination controls, but doesn't explicitly state when not to use or list alternatives.

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