Shipping_getCarrierAccountFormInputs

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

With no annotations, the description carries the burden of behavior. It does indicate that this is a return-style, non-mutating operation and adds an execution-environment caveat ('Runs in your Kuudo deployment, not here'), but it does not mention permissions, failure modes, or whether the returned data varies by carrier.

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 core sentence is concise and front-loaded with the key behavior. However, 'Catalog entry.' is vague filler, and 'Runs in your Kuudo deployment, not here' is unclear without further explanation, so not every sentence fully earns its place.

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 zero-parameter catalog endpoint, the description gives the essential purpose but omits useful context such as whether the returned input schema is carrier-specific, how the form inputs should be used afterward, or any response structure. The absent output schema increases the need for a bit more return-value detail.

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 tool has zero parameters and an empty schema, so no parameter documentation is needed. The baseline of 4 applies because description does not need to compensate for undocumented parameters.

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 ('return') and resource ('a list of input schema required to register a shipper account with the carrier'). This clearly differentiates it from sibling tools such as getCarrierAccounts and linkCarrierAccount, which address different parts of the carrier-account workflow.

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?

No guidance is given about when to use this tool versus alternatives like Shipping_getCarrierAccounts or Shipping_linkCarrierAccount. The note about running in the user's Kuudo deployment is context, but it does not explain the calling workflow or when this endpoint should be preferred.

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