dolibarr_list_thirdparties

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

No annotations provided, so description carries burden. It indicates this is a list operation with filtering/pagination, implying read-only behavior. However, does not explicitly state that it's non-destructive or require any authorization, leaving room for ambiguity.

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, no unnecessary words. Front-loaded with the main purpose, efficiently covers filtering and pagination. Every sentence earns its place.

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 well-documented schema (80% coverage), the description is adequate. It communicates the core functionality and distinguishes from other list tools. Could be enhanced with examples of filter strings, but not necessary for basic use.

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 80%, so most parameters are documented in the schema. The description adds 'basic filtering and pagination' which hints at the filter and pagination parameters, but adds minimal new meaning beyond the schema.

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 'List thirdparties (clients/suppliers)' with a specific verb and resource. It distinguishes from siblings like dolibarr_get_thirdparty (single) and dolibarr_create_thirdparty, but could be more explicit about listing all vs. specific thirdparties.

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?

Mentions 'basic filtering and pagination', indicating when to use it, but no explicit when-not or alternatives provided. Lacks guidance on when to prefer this over similar tools like dolibarr_find_thirdparty_by_email.

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