dolibarr_list_contracts

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

No annotations exist, so the description must fully disclose behavioral traits. It only states 'List contracts', failing to mention read-only nature, pagination behavior, rate limits, or any side effects. The agent cannot infer safety or performance characteristics.

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 extremely concise (4 words) but at the cost of being under-specified. For a tool with four parameters and no other documentation, this brevity leaves critical information missing, making it insufficient rather than efficient.

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?

Given the absence of annotations, output schema, and parameter descriptions, the description must compensate but fails entirely. It omits details about parameter behavior, response format, and operational constraints, leaving the tool largely unexplained.

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 coverage is 0% with no parameter descriptions. The description does not explain what parameters like limit, sortfield, sortorder, or sqlfilters mean, nor their constraints or typical use. The agent must guess their semantics from names alone, risking misuse.

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 action (list) and resource (contracts in Dolibarr), making the basic purpose unambiguous. However, it does not distinguish this tool from sibling list tools like dolibarr_list_invoices or dolibarr_list_proposals, which share the same verb and similar resource patterns.

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 provides no guidance on when to use this tool versus alternatives (e.g., dolibarr_get_contract for a single contract) or any context about prerequisites or limitations. The single sentence offers no usage strategy.

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