Reverse-charge (§13b) report

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

Declares 'Read-only' behavior, which is critical. No annotations, so description carries full burden. Discloses that it lists mismatched vouchers, adding transparency about edge cases.

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 paragraph with clear structure: main action, breakdown by meaning, and note on mismatched vouchers. Front-loaded with purpose, no wasted words.

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?

Given complexity of reverse-charge reporting, description defines categories and mentions mismatched vouchers. No output schema, so return value description is vague but sufficient for high-level understanding.

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 baseline is 3. Description does not elaborate on parameters like 'from', 'to', 'rate', or 'maxVouchers' beyond schema's own descriptions.

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 uses specific verb 'Total' and identifies resource 'reverse-charge (§13b) tax base.' Clearly states the split by meaning and distinguishes from sibling tools like sevdesk_audit_vat by focusing on reverse-charge reporting.

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?

No explicit when-to-use or when-not-to-use guidance. It describes output categories and mentions mismatched vouchers, implying use for reverse-charge reporting but lacks comparison with alternatives.

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