Create Saved Filter

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

With readOnlyHint=false in annotations, the mutating nature is already disclosed. The description adds minimal behavioral context beyond the annotation, mainly the two modes of defining conditions, which is also described in the schema. No contradiction exists.

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, concise sentence that front-loads the verb and resource. Every word adds value and no unnecessary details are included.

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?

Given the detailed schema and presence of an output schema, the description adequately conveys the tool's purpose. It doesn't need to explain return values. Missing explicit mention of prerequisites or side effects, but those are not critical for a create operation with clear schema coverage.

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 description coverage is 100%, so parameters are already well-documented. The description's mention of 'query or field conditions' adds little new meaning beyond the schema, which already notes mutual exclusivity. Baseline 3 applies.

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 action ('Create') and the resource ('saved Yandex Tracker issue filter'), and mentions the two ways to define it ('using query or field conditions'). It distinguishes from sibling tools like filter_update (which modifies) and filter_get (which retrieves) by focusing on creation.

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 verb 'create' implies this is for new filters, but there is no explicit 'when to use vs alternatives' or mention of filter_update for existing filters. The usage is implied rather than clearly stated, so it meets the 'implied usage' bar but not higher.

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