Lista ofert EstiCRM

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

The description repeats the read-only behavior already declared by readOnlyHint=true, which adds little. It does add useful behavioral context by describing the result as 'ograniczoną, stronicowaną listę', indicating pagination and a bounded result set. No contradiction with annotations exists.

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 two short sentences, front-loaded with the core action and scope. It contains no filler or unnecessary detail, though the read-only statement is somewhat redundant with the annotations.

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 simple read-only paginated list, the description covers the basic invocation needs, and the output schema can supply return-shape details. It is less complete as a standalone guide because it does not clarify when to choose this list over sibling offer-related tools.

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 schema documents 'limit' but not 'strona', and the description's mention of pagination helps hint at the meaning of 'strona'. However, the description does not explicitly explain the page parameter or its relationship to the list, leaving some inference required.

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 states a specific verb and resource: 'Pobiera ... listę ofert' (retrieves a list of offers), and adds that the list is limited and paginated. It is clear, but it does not explicitly distinguish itself from siblings like esticrm_oferty_klienta or esticrm_szczegoly_oferty.

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 description gives no guidance on when to use this tool versus alternatives. It conveys only what the tool does, not when it should be preferred over esticrm_oferty_klienta or esticrm_lista_inwestycji.

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