contact_template_list

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

With no annotations provided, the description must fully disclose behavioral traits such as pagination, filtering, or return payload. The description gives none of this context, offering only a generic resource label.

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 short, but under-specification is not conciseness. The single phrase adds little value beyond the tool name and does not earn its place, as it fails to communicate the operation or context.

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 complexity (5 parameters, output schema, multiple sibling template tools), the description is critically incomplete. The agent cannot determine what this tool returns, when to use it, or how it differs from contact_list or task_template_list.

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 five parameters have rich descriptions in the input schema (100% coverage), so the schema already explains field meanings, defaults, and constraints. The description adds no additional parameter semantics, but the high schema coverage meets the baseline.

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 is a noun phrase ('Шаблоны контактов и компаний') that merely restates the resource implied by the tool name 'contact_template_list'. It does not specify the action (list/get) and fails to distinguish this tool from sibling tools like contact_list or contact_group_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?

No guidance is provided about when to use this tool versus alternatives. There is no mention of the intended use case, prerequisites, or exclusions, leaving the agent without context for tool selection.

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