communicate_sales_document_at

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

No annotations provided, but description discloses triggers a webservice, requires finalized doc, confirm must be true, and response carries AT status. Could mention irreversibility explicitly.

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 sentences, each adding unique value: purpose, internal action, precondition, response. No redundant 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?

Covers purpose, preconditions, and response content. With output schema present, description is sufficient. Minor omission: error scenarios not mentioned.

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%; description reinforces id must be finalized and confirm must be true (as in schema). Adds webservice context but minimal extra value over schema.

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 tool communicates a finalized sales document to the AT (Portuguese tax authority), distinguishing it from siblings like finalize_sales_document and communicate_purchase_document_at.

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?

Specifies that the document must be finalized and that confirm=true is required due to binding fiscal submission. Implicitly excludes non-finalized documents, but could explicitly mention the prerequisite finalize_sales_document tool.

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