Task Filter Options

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds 'live item count', indicating real-time counts, and a performance note about being cheaper, which goes beyond the structured annotations and gives useful behavioral context.

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 a single sentence that front-loads the action ('Get the valid filter values'), lists the categories, and adds a cost-benefit rationale. Every phrase earns its place, with no redundancy or fluff.

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?

For a one-parameter, read-only tool with no output schema, the description sufficiently explains what the response contains (valid filter values with live counts) and when to use it. It could optionally mention how these values feed into task_list filtering, but the core usage is clear.

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?

The schema has 100% coverage for the only parameter 'project' with a description 'Project id'. The description does not add further parameter details, but the baseline of 3 applies because the schema fully documents the parameter and the description's mention of 'in a project' aligns with it.

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 starts with 'Get the valid filter values' and lists statuses, tags, assigned users, and roles, clearly identifying the resource (tasks in a project). It also distinguishes itself from the sibling task_list by noting it is 'cheaper than a full task_list call just to discover ids'.

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 explicitly frames the tool as a cheaper alternative to task_list for discovering valid filter IDs, giving clear context on when to use it over that sibling. It does not explicitly mention other alternatives like user_story_filters_data, but the task-specific scope is clear.

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