Wydarzenia kalendarza EstiCRM

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds meaningful behavioral context by saying the result is 'ograniczoną listę' (a limited list), which hints at result-set boundaries, and clarifies that the calendar is identified by an agent email.

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?

A single front-loaded sentence states the verb, resource, and key scoping detail without filler or repetition. Every word contributes meaning.

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?

An output schema is present and the annotations cover the safety profile, so those aspects do not need to be restated. The description adequately identifies the calendar and result-set nature; the date-range and limit parameters are documented in the schema, making the definition sufficient for correct invocation.

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 descriptions already cover 'od', 'do', and 'limit'. The description adds value for the undocumented 'kalendarz' parameter by indicating that the calendar is specified through the agent's email address, and 'ograniczoną listę' maps to the limit behavior.

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' - fetches) and names the resource precisely: a limited list of events from a calendar indicated by the agent's email address. This clearly distinguishes it from sibling tools, none of which are described as calendar-event retrieval.

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?

Usage is implied: use when you need a bounded list of events from a specific agent's calendar. The description gives useful context by specifying the calendar is selected via the agent's email, but it does not name alternatives or state when not to use this tool.

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