list_accounts

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

No annotations are present. The description implies a read-only operation but does not disclose any side effects, authentication requirements, or behavior such as pagination or ordering.

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 phrase, concise and front-loaded with the essential verb and resource. No unnecessary words.

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 no output schema, the description does not specify what fields or format the list of accounts contains. It lacks details on authentication, result structure, or potential limitations.

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 input schema is empty and 100% covered by the schema itself. The description adds no additional parameter meaning, which is acceptable for a parameterless tool.

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 'Список доступных аккаунтов HuntFlow' clearly states the verb (list) and resource (accounts of HuntFlow). It distinguishes from sibling tools which focus on applicants, vacancies, and stages.

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 on when to use this tool versus alternatives like list_vacancies or search_applicants. The description does not provide context for usage scenarios or exclusions.

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