FbaInboundEligibility_getItemEligibilityPreview

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

With no annotations, the description carries the full burden of behavioral disclosure. It implies a read-only operation through 'gets', but it does not state side effects, permissions, limitations, return behavior, or what 'Runs in your Kuudo deployment, not here' actually means for invocation.

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 efficient, but the opening 'Catalog entry. Runs in your Kuudo deployment, not here.' is opaque and front-loaded before the actual operation. It adds confusion rather than clear context.

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 is incomplete for reliable invocation: it does not explain how to specify the item, what the preview contains, or what execution in the 'Kuudo deployment' means. The empty schema and absent output schema increase the need for this missing context.

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, yet the description says 'an item that you specify', implying a required identifier that is never named or structured. The additionalProperties: true leaves an agent guessing what keys to supply, so the description fails to add usable parameter meaning.

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 clear operation: it gets an eligibility preview for an item the caller specifies. This is specific enough to convey the resource and action, though it does not distinguish it from similar sibling tools like Awd_checkInboundEligibility.

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, and does not mention any exclusions. The phrase 'Runs in your Kuudo deployment, not here' hints at an execution context but does not help an agent decide when to select this operation.

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