Dane klienta EstiCRM

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

Annotations already provide readOnlyHint and idempotentHint. The description adds a meaningful behavioral detail beyond annotations: contact data are hidden by default and only appear when the parameter is explicitly set. This helps the agent avoid assuming full data will always come back.

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?

Two short sentences, each earning its place: the first states the core purpose, the second surfaces an important default behavior. No filler or redundant repetition of schema fields.

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 low-complexity tool with an output schema, rich annotations, and only two parameters, the description is sufficient. The key gotcha—hidden contact data—is disclosed, and the schema covers parameter syntax and defaults.

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 description coverage is only 50%, so the description should compensate. It does clarify the behavior of pokaz_dane_kontaktowe, but it adds little semantic meaning for id_klienta beyond what the property name already implies. Partial compensation only.

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 dane jednego klienta' (retrieves data of one client). This clearly distinguishes it from sibling tools, which target offers, agents, locations, dictionaries, calendar events, investments, and offices.

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 clear: call this tool when you need data for a single client. It does not name alternatives explicitly, but none of the sibling tools appear to compete for the same job, so the lack of exclusionary guidance is minor.

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