Invoices_getGovernmentInvoiceDocument

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

With no annotations, the description must disclose behavioral traits itself, but it only states the return shape and the deployment caveat. It does not explicitly confirm that this is a read-only operation, mention authentication requirements, or explain side effects. The 'not here' statement is useful but insufficient for full behavioral transparency.

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 short and front-loads the key facts: deployment context and return value. No sentence is wasted, though 'Catalog entry' is somewhat vague and could be removed or clarified.

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 tool is simple with no parameters and no output schema, so the description need not be extensive. It does explain the main return value, which helps an agent know what to expect. However, it lacks any reference to related invoice tools, usage context, or what an invoiceDocumentUrl represents, leaving some gaps for a zero-context agent.

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 has zero parameters and 100% schema coverage, so there are no parameter semantics for the description to explain. Per the rubric, zero parameters warrants a baseline of 4, and the description doesn't need to add parameter detail.

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 specific action and resource: 'Returns an invoiceDocument object containing an invoiceDocumentUrl.' This is clear enough to identify what the tool does. However, it does not differentiate itself from closely named siblings like Invoices_getInvoicesDocument or Invoices_getGovernmentInvoiceStatus, and the opening 'Catalog entry' adds ambiguity rather than clarity.

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 gives no guidance on when to use this tool versus alternatives. It mentions 'Runs in your Kuudo deployment, not here,' which is an environment caveat, but it does not specify conditions, exclusions, or which sibling tools to prefer. There is no actionable usage recommendation.

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