ksef_submit_invoice

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

Annotations already flag destructive and idempotent. Description reinforces with 'irreversibly' and adds 'legally binding' context. No contradictions. Adequately discloses key behavioral traits beyond annotations.

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 sentences, no fluff, front-loaded with purpose. 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?

With one parameter, annotations covering destructive/idempotent, and existence of output schema, the description covers purpose, prerequisite, and irreversibility. Lacks failure mode details but adequate for simple tool.

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?

Single parameter 'confirmation_token' has 0% schema description coverage. Description explains its purpose (from ksef_prepare_invoice) but not format or constraints. Provides minimal but useful context connecting to sibling tool.

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?

Explicitly states it 'irreversibly issues a legally binding invoice to KSeF', giving a specific verb and resource. Distinguishes from siblings like ksef_prepare_invoice by noting prerequisite token.

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?

Clearly states prerequisite ('Requires a confirmation_token from ksef_prepare_invoice'), implying the tool is used after preparation. No explicit when-not-to-use, but context is sufficient for typical workflow.

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