Shipping_getCarrierAccounts

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

No annotations are provided, so the description must disclose behavior on its own. It adds one useful piece of context ('Runs in your Kuudo deployment, not here') but omits whether the call is read-only, what authorization is required, what response to expect, or any side effects.

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, but the first token 'Catalog entry' is unnecessary and confusing, and 'return Get all' is grammatically broken. Not every sentence earns its place, and the useful information is buried after the confusing opening.

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?

For a tool with no annotations and no output schema, the description leaves important gaps: the expected return data shape, authentication/permissions, and how the merchant is determined. The deployment note helps, but the overall context is insufficient for an agent to invoke this confidently.

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 full coverage, so the description is not required to document parameters. The 'for a merchant' phrase implies a merchant context, but since no parameter is exposed, the baseline of 4 is appropriate.

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 the main operation: return all carrier accounts for a merchant, which is a specific verb and resource. However, the wording 'return Get all' and the opening 'Catalog entry' add noise, and it does not explicitly differentiate from sibling carrier-account tools.

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 about when to use this tool instead of alternatives like linkCarrierAccount, unlinkCarrierAccount, or getCarrierAccountFormInputs. The description only gives a deployment note and a restatement of the operation, so an agent must infer usage from the name.

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