Get E-Invoice Status

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

Description adds value beyond annotations: polling recommendation, honest 'unavailable' response for missing backend, and return fields (step, ack ID, URLs). No contradictions with 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?

Four effective English sentences, front-loaded with verb and purpose. Spanish translation adds length but doesn't harm. Could be slightly leaner.

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?

Covers behavior, polling advice, truthfulness, and return values. Output schema likely details return structure. Adequate for a polling tool with clear sibling context.

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% with existing description. Description adds context that workflowRunId comes from send_einvoice, but schema already covers meaning.

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 polls e-invoice workflow status, with specific verb 'Poll the status' and resource 'e-invoice dispatch workflow'. It distinguishes from siblings like send_einvoice by focusing on status 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?

Provides explicit polling interval (5-10 seconds) and terminal statuses. Does not explicitly mention when not to use or alternatives, but context implies it follows send_einvoice.

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