defaults_invoice

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

With no annotations, the description carries the burden. It discloses what data is returned (VAT rates, currencies, payment terms, etc.) and specifies the source for exchange rates (BNR, current). It does not mention side effects (none expected) or error behavior, but for a read-only getter this is reasonably transparent.

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 informative but not bloated. It lists the key contents in a single sentence, followed by a clear usage directive. The only minor redundancy is 'needed for invoice creation' and 'Always fetch this before creating invoices', but it remains concise overall.

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?

There is no output schema, so the description must compensate. It lists high-level categories but does not specify the response structure, exact field names, or nested objects. An agent would need additional information to parse the response confidently, leaving a moderate gap.

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 description fully covers the only parameter (companyId) with 'Company UUID override (uses active company if not set)', so schema coverage is 100%. The tool description adds no extra detail, matching the baseline of 3 for well-documented parameters.

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?

States a specific verb ('Get') and clearly describes the resource: default values and dropdown options for invoice creation. It enumerates the exact contents (VAT rates, currencies, payment terms, etc.), making its purpose unmistakable and distinguishing it from other sibling list endpoints.

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?

Provides explicit guidance: 'Always fetch this before creating invoices — never hardcode these values.' This tells the agent exactly when to use this tool and warns against a common anti-pattern, effectively setting usage expectations.

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