Отложенные действия

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

The description explains that both completed and cancelled tasks are shown by default and that the status parameter can filter them, which adds behavioral nuance beyond the readOnlyHint and destructiveHint annotations. It does not describe return format or pagination, but those are not critical for a list operation with an output schema.

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, focused sentence that provides an illustrative example and a practical filtering tip. It is concise, front-loaded with the core concept, and contains no redundant information.

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 tool's simplicity, the description covers its main behavior (showing deferred actions) and notes that completed/cancelled are included. Combined with the detailed parameter schema, an agent has enough context to invoke it correctly. It could be slightly more explicit about it being a read-only listing, but the annotations already convey that.

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 parameters are fully described in the input schema (100% coverage), so the description does not need to repeat them. The mention of 'select by status' slightly reinforces the status parameter's purpose but adds little beyond the schema's own description.

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 tool's purpose: it shows deferred actions planned in a case, with examples that illustrate the concept. It distinguishes itself from sibling tools like tasks_cancel by focusing on listing and filtering rather than modifying tasks.

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 gives clear context on when to use this tool (to see what's planned in a case) and hints at filtering by status to include completed/cancelled tasks. It does not explicitly mention alternatives or exclusions, but the sibling list makes it obvious this is the primary listing tool for tasks.

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