contact_list

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

No annotations exist, so the description carries the full burden of behavioral disclosure. It only states a list of contacts and companies, omitting details like default value of isCompany, pagination, filtering capabilities, or response behavior.

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 terse—a single noun phrase—which borders on under-specification rather than effective conciseness. It omits essential operational details and doesn't earn its place as a helpful guide.

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 (9 parameters, output schema, no annotations), the description is far too minimal. It fails to add context about how to construct requests, interpret results, or handle filters, leaving the agent to rely entirely on the schema.

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?

With 89% schema description coverage, parameters are well-documented in the schema (e.g., fields, offset, filters, pageSize, isCompany). The description itself adds no extra parameter context, 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 'Список контактов и компаний' identifies the resource as a list of contacts and companies but lacks an explicit verb like 'list' or 'retrieve'. It distinguishes from siblings like contact_by_id and create_contact, but is vague about scope or action.

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 given on when to use this tool versus alternatives like contact_by_id. There is no mention of prerequisites, typical use cases, or when filtering/pagination is appropriate.

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