dolibarr_get_invoice

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

No annotations provided. Description states read operation but does not disclose error behavior, permissions, or rate limits. Adequate for simple get, but minimal.

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?

Single sentence, no wasted words, key information front-loaded.

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?

Covers what is returned (lines, payment status). No output schema, but for a simple get tool, description is sufficient. Missing error cases but minimal impact.

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 0%, description adds 'by ID' context but does not explain that id is the invoice identifier beyond schema. Some added value, but could be more explicit.

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?

Clear verb 'Get' and resource 'single invoice', with scope 'including its lines and payment status' and method 'by ID'. Distinguishes from siblings like list_invoices or create_invoice.

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?

Implies usage when retrieving a specific invoice with details, but no explicit when-not or comparison to alternatives like list_invoices or validate_invoice.

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