task_template_list

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

The description provides no behavioral information beyond what the schema already includes. With no annotations, the description carries the full burden but discloses nothing about pagination, default behavior, or output characteristics, making it wholly uninformative.

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 extremely concise and easy to read, but it is more of a title than a description. It is not bloated, but it is also under-specified, lacking the structure of a useful tool description.

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 simple list tool, the description only names the resource. It does not explain what a task template is, what the list contains, or any practical context. The presence of an output schema covers return values, but the description is still inadequate for an agent to understand the tool's full purpose.

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?

All four parameters have rich descriptions in the schema (100% coverage), so the description adds no additional meaning. The schema fully documents fields, offset, pageSize, and sourceId, so the bare description does not need to compensate.

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 'Список шаблонов задач' (List of task templates) clearly identifies the resource and action (list), and distinguishes it from sibling tools like project_template_list and contact_template_list. However, it lacks an explicit verb and is phrased as a title rather than a full sentence.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of filtering, typical use cases, or context that would help an agent decide between this and other list tools.

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