Get Work Activity Filter Options

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds the API endpoint and return type (JSON array of filter values), but does not go beyond what annotations imply about 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 short but contains a contradictory sentence and redundant mention of the API endpoint. It is not clean or efficient.

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?

Missing key context: why choose this version over siblings (e.g., v1_0_2), no explanation of pagination despite page/per_page parameters, and return format is vaguely described. The contradictory statement reduces 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?

Input schema has 100% parameter descriptions, so baseline is 3. Description only restates project_id as required and does not add meaning to page/per_page parameters.

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 near misses, but then incorrectly says to fetch full details of a specific incident, which is contradictory and misleading for the agent.

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 only usage guidance provided is to fetch incident details, which is inaccurate for this tool. There is no mention of when to use this vs. other filter option tools or versions.

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