Lista inwestycji EstiCRM

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, covering the safety profile. The description adds that the returned list is 'ograniczoną' (limited), which is a useful behavioral hint, but does not disclose much beyond that and the schema already conveys limits.

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 a single, front-loaded sentence with no filler. Every word contributes to identifying the operation and resource.

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 list tool with output schema and safety annotations, the description is mostly adequate. But it lacks explicit parameter semantics for 'fraza' and any usage context relative to sibling list tools, leaving an agent to infer important calling details.

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 describes 'limit' explicitly, and the description's mention of filtering gives some clue that 'fraza' is a filter parameter. However, the description does not clarify how 'fraza' behaves (e.g., partial match, which fields are searched), so it only marginally compensates for the missing schema description on that parameter.

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 clear verb ('Pobiera' - retrieves) with an explicit resource ('listę inwestycji'), and the resource makes it distinguishable from sibling tools like esticrm_lista_ofert. However, the phrase 'lub filtruje ograniczoną listę' introduces some ambiguity about whether this returns a bounded subset or filters by criteria.

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 sibling tools, no mention of alternatives, and no exclusions. The intended use is only implied by the name and resource, not explicitly stated.

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