kommo_list_companies

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

No annotations exist, so description carries full burden. It does not disclose pagination behavior, rate limits, or authorization requirements. The phrase 'list all companies' may mislead agents into expecting all results without pagination.

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 very concise (4 words) but lacks critical information. It is appropriately sized for a simple concept but overly terse, sacrificing clarity and completeness.

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 tool with pagination parameters and no output schema, the description is incomplete. It does not explain the pagination nature, default limits, or response format, leaving agents to infer behavior.

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?

Schema coverage is 0% and description does not mention parameters 'page' and 'limit'. Since there are 2 parameters and schema provides no descriptions, the tool description fails to add meaning or usage details.

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?

Description states 'List all companies' which clearly identifies the verb (list) and resource (companies). However, it does not differentiate from sibling list tools like kommo_list_contacts or kommo_list_deals, and the word 'all' is ambiguous given pagination parameters.

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 provided on when to use this tool versus alternatives. For example, there is a sibling kommo_search_company for search, but description offers no context on choosing between list and search.

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