tasks_my

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

With no annotations, the description carries the full burden. It usefully discloses deduplication and the union of executor/assignor roles, but omits any mention of return format, pagination, status handling, or side effects. This is partial but not comprehensive disclosure.

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?

A single, tightly-phrased sentence communicates the tool's purpose without any waste. It is front-loaded with the tool name and immediately explains the unique behavior.

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?

The tool has 4 optional params and no output schema or annotations. The description explains the core behavior, but lacks return value details and usage context. It is a minimum-viable description for a list/read tool, not a full specification.

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% with all four parameters documented in the input schema. The tool description adds no extra parameter meaning, so the 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 the tool combines tasks where the user is the executor and where the user is the assignor, with deduplication. This is a specific verb (объединить) + resource (задачи) and clearly distinguishes from generic task listing tools like tasks_list.

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 implies use for retrieving the current user's combined tasks, but provides no explicit when-to-use guidance or alternatives. It does not mention when to prefer this over tasks_list or tasks_search_text.

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