VendorDirectFulfillmentShipping20211228_getCustomerInvoices

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose one notable trait—the tool runs in the Kuudo deployment, not in this environment—and labels itself a 'Catalog entry,' but it omits details such as pagination, return shape, error behavior, or whether the call is read-only.

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?

Two sentences with minimal waste; the core return behavior is front-loaded. The fragment 'Catalog entry' is cryptic and earns little keep, but the overall length is appropriate for a lightweight catalog-style tool.

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?

With no output schema, no annotations, and an empty input schema, the description is the only operational guidance an agent gets. It states the purpose and a runtime caveat, but leaves out return format, pagination, error conditions, and any differentiation from the near-twin getCustomerInvoice sibling. It is adequate as a catalog stub but thin as an executable spec.

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 properties, so the description is the sole source of parameter meaning. It supplies the only semantic hint: a time frame that the caller specifies. Given the 0-param baseline of 4, the description adds usable meaning despite the schema being empty and permissive.

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 verb ('Returns'), a resource ('a list of customer invoices'), and a qualifier ('created during a time frame that you specify'), so an agent knows exactly what the tool does. It does not explicitly differentiate from sibling getCustomerInvoice (singular) or the V1 getCustomerInvoices variant, but the core function is unambiguous.

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?

There is no guidance on when to use this tool versus the singular getCustomerInvoice, the V1 getCustomerInvoices, or the other shipping invoice tools. The 'Runs in your Kuudo deployment, not here' note hints at an operational constraint but provides no selection criteria for choosing among siblings.

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