Invoices_getInvoicesExports

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

With no annotations, the description carries the behavioral burden. It adds a meaningful runtime caveat ('Runs in your Kuudo deployment, not here') and 'Returns' implies a non-mutating lookup. However, it does not clarify what 'Catalog entry' means for execution, whether auth or rate limits apply, or how results are presented.

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 short and mostly front-loaded, with the execution caveat placed early. The opening fragment 'Catalog entry.' is somewhat vague and could be considered noise, so it is not perfectly efficient.

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 covers the core operation and the critical environment caveat, but with no output schema and no filter details, an agent does not learn the response structure or how to form filters. The sibling ambiguity also remains unresolved, leaving the description minimally adequate rather than complete.

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 schema declares zero parameters and baseline for no params is 4. The description adds the concept of 'filters that you specify', which is useful given additionalProperties is true, letting the agent know arbitrary filter properties may be accepted. It still does not enumerate valid filter names or value formats.

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 identifies a read operation: it 'returns invoice exports details' for matching filters, naming the resource and action. However, it does not differentiate this from sibling tools like Invoices_getInvoicesExport or Invoices_getInvoices, so it falls short of full sibling distinction.

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 phrase 'for exports that match the filters that you specify' implies use when a filtered list of invoice exports is needed, and 'Runs in your Kuudo deployment, not here' gives an environment constraint. It does not explicitly state when to prefer this tool over its siblings or list exclusions, so the guidance is only implicit.

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