Lista agentów EstiCRM

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

Annotations already cover safety via readOnlyHint, idempotentHint, and destructiveHint=false. The description adds one useful behavioral constraint—the response is limited and omits contact data—but does not describe pagination, sorting, or result availability. This is helpful but not rich behavioral context.

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 one focused sentence with no filler. It front-loads the action and resource, then states the key limitation. Every phrase earns its place and matches the low complexity of the tool.

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 one-parameter list operation with full schema coverage, an output schema, and safety annotations, the description is nearly sufficient. It clearly states the tool returns a limited agent list without contact data, though response details are mostly delegated to the output 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?

Schema coverage is 100%, and the sole 'limit' parameter has a complete schema description: 'Maksymalna liczba rekordów w odpowiedzi.' The description's phrase 'ograniczoną listę' loosely reflects the limit concept but adds no new parameter semantics beyond what the schema already provides.

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 uses a specific verb ('Pobiera' - retrieves) and resource ('listę agentów'), and adds a distinctive scope: a limited list without contact data. This differentiates it from sibling list tools such as esticrm_lista_ofert, esticrm_lista_biur, and esticrm_lista_inwestycji, and from tools that would expose contact details.

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?

The intended use is implied: get a bounded list of agents when contact details are not needed. However, it does not explicitly name alternatives, give when-not-to-use conditions, or explain how it differs from sibling tools beyond the resource type.

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