ksef_render_invoice_pdf

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

Description only states it renders a locally. With annotations having all hints false, the description does not disclose side effects, whether it modifies the XML, or file handling behavior (e.g., overwriting). Minimal behavioral information beyond the action.

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 of 16 words, highly concise with the core information front-loaded. No unnecessary text.

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?

Description is insufficient given 4 parameters, 1 required, and available output schema. It does not explain prerequisites (e.g., confirmation_token from ksef_prepare_invoice) or output format. Context about the workflow is missing.

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 description coverage is 0%, and the description does not explain any parameter meaning or usage. The description adds no value beyond the schema's parameter names and types.

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?

Description clearly states the verb 'Render', the resource 'local KSeF-like PDF', and the key distinction 'from prepared FA(3) XML without sending to KSeF', effectively distinguishing from sibling tools like ksef_submit_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?

The phrase 'without sending to KSeF' implies when not to use this tool, but it does not explicitly name alternative tools or provide direct usage guidance. It lacks clear when-to-use and when-not-to-use compared to siblings.

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