Invoices_getInvoicesDocument

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

With no annotations provided, the description carries the burden of explaining behavior. It does disclose the return value ('ID and URL') and the notable fact that it runs remotely ('in your Kuudo deployment, not here'). However, it omits any details about required context, permissions, URL semantics, or likely side effects, leaving the behavioral picture incomplete.

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 very compact and contains no verbose filler, but it opens with the cryptic 'Catalog entry' and puts the core function last. The structure could be improved by front-loading the return behavior and adding a brief sibling qualifier.

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?

The description is too thin for a tool with no output schema and several close sibling tools. It does not explain which document is returned, how the document ID relates to other invoice endpoints, or what the returned URL is actually for. The 'Kuudo deployment' remark is opaque and does not resolve these gaps.

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?

The input schema declares zero parameters and schema description coverage is 100%, so there is little for the description to add about parameters. The description correctly avoids inventing parameter details. The schema's 'additionalProperties: true' is unexplained, but the zero-parameter baseline of 4 applies.

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 states a concrete action and resource: it 'returns the invoice document's ID and URL.' This is more than a tautology and distinguishes the tool as a retrieval operation for invoice documents. However, it does not explicitly differentiate from the sibling tool Invoices_getGovernmentInvoiceDocument or clarify what an 'invoice document' is relative to an 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 description provides no explicit when-to-use, when-not-to-use, or alternative tool guidance. The phrase 'Runs in your Kuudo deployment, not here' is a deployment caveat, not a usage recommendation, and it does not help the agent choose between this tool and related siblings like Invoices_getInvoice or Invoices_getGovernmentInvoiceDocument.

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