einvoice_submit

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false; the description adds genuinely useful behavior beyond that: non-ANAF providers generate country-specific XML and only call the remote API if credentials are configured, which tells the agent the effect can be either local generation or an external irreversible submission. It does not cover failure modes, retry safety, or what is returned after a submission.

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?

Three sentences, front-loaded with the action, then the provider matrix, then the behavioral branch. Efficient and scannable; the only waste is the provider list being restated from the enum.

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 3-parameter mutation tool with no output schema, the description covers what is submitted, where it goes, and the conditional remote call, which is enough to call it correctly. Missing is the post-submission picture (does it return a submission id, is it tracked by einvoice_submissions) and any precondition on invoice state.

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 100%, so all three parameters (uuid, provider, companyId) are already documented, and the provider list in the description merely repeats the enum description. The description adds no meaning about the uuid's expected invoice state or what companyId defaulting entails, so the baseline 3 applies.

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 and resource ("Submit an invoice to an e-invoicing provider") and enumerates the five supported providers with country mapping. It is clear what the tool does, though it never names the closest sibling (invoices_submit) to say how they differ, leaving the agent to infer the boundary.

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 provider list implies when to use it, and the sentence "For ANAF, uses the existing e-Factura submission flow" hints at a relationship to the ANAF tooling. But with siblings like invoices_submit, einvoice_providers and einvoice_config_test present, the description gives no explicit rule for choosing this tool over them and no stated prerequisites (e.g., must the invoice be issued first, must config exist?).

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