Get Work Activity Filter Options

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

Annotations already declare readOnlyHint, destructiveHint, and idempotentHint. The description adds little beyond stating it returns a JSON array, but includes an inaccurate statement about fetching incident details. It does not disclose pagination behavior or response structure, leaving behavioral gaps despite good annotation coverage.

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 four sentences long. The first sentence is concise, but the second is confusing and irrelevant. The third and fourth are redundant with schema and endpoint info. Could be shorter and more focused.

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 is provided, so the description should explain the response structure in more detail. It only says 'JSON array of available filter values for Incidents' without describing the items. It also fails to differentiate this version from its siblings (v1_0, v1_0_2, v1_0_4), leaving context incomplete.

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 all parameters are documented. The description redundantly states 'Required parameters: project_id' without adding new meaning. 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 states it returns work activities for filtering property damages, providing a clear verb+resource. However, it also includes a misleading statement about fetching full details of a specific incident, which creates confusion and reduces clarity. It does not distinguish from versioned siblings like v1_0, v1_0_2, etc.

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?

No guidance on when to use this tool versus alternatives (e.g., other filter options tools). The description incorrectly suggests it can be used to fetch incident details, which is not the tool's purpose. No context on 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.