holded_list_contacts

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

Without annotations, the description carries the full burden of disclosing behavior. It conveys a read-only list action and the optional type filter, but does not mention output structure, pagination, or any edge cases beyond the schema. The basic behavior is clear, but richer disclosure is absent.

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 with no filler. The main action is front-loaded and the optional filter is stated efficiently. Every word contributes to understanding.

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 list tool with one optional parameter, no output schema, and no annotations, the description covers the essential purpose and scope. It could be completeer by naming the debtor/creditor enum values or indicating the response shape, but that is a minor gap given the tool's simplicity.

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 100%, and the parameter's own description ('Filter by contact type') plus enum fully define the valid values. The description only reiterates that filtering is optional, adding little beyond the schema. Baseline 3 is appropriate because the schema already covers the 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 clearly states the tool lists all Holded contacts (customers and suppliers) and can optionally filter by type. It specifies a concrete verb and resource, but does not explicitly distinguish itself from sibling tools like holded_get_contact, relying instead on the obvious singular/plural difference.

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?

There is no guidance about when to choose this tool over alternatives such as holded_get_contact or holded_list_accounts. The statement 'optionally filters by type' only describes parameter usage, not tool-selection context or exclusions.

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