einvoice-mcp

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

With no annotations provided, the description carries full burden but provides minimal behavioral information. It mentions what formats can be converted but doesn't disclose important traits like whether this is a read-only operation, potential side effects, error handling, performance characteristics, or authentication requirements. The description doesn't contradict annotations (none exist), but fails to provide adequate behavioral context.

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 extremely concise with zero wasted words. It's front-loaded with the core purpose in the first sentence, followed by specific conversion directions. The bilingual presentation (German/English) is efficient for clarity. 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?

Given the tool's complexity (format conversion with multiple directions), no annotations, and no output schema, the description is insufficient. It doesn't explain what the tool returns, error conditions, input format requirements beyond basic mentions, or how validation works. For a data transformation tool with 3 parameters, this leaves significant gaps in 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?

With 100% schema description coverage, the baseline is 3. The description adds some value by listing all six conversion directions, which helps understand the 'direction' parameter's enum values, but doesn't provide additional semantic context beyond what's already in the schema descriptions for 'input' and 'validate_output' 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?

The description clearly states the tool's purpose with specific verbs ('konvertiert', 'converts') and resources ('E-Rechnungen', 'e-invoices'), and explicitly lists all six conversion directions. It distinguishes itself from sibling tools by focusing on format conversion rather than creation, extraction, validation, or information retrieval.

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 description provides clear context about when to use this tool (converting between UBL, CII, and JSON formats), but doesn't explicitly state when NOT to use it or mention alternatives. It doesn't compare with sibling tools like 'get_format_info' or 'validate_invoice' that might be relevant in some scenarios.

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