list_inventory_items

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

With no annotations provided, the description carries the full burden. It notes OData filtering support and listing items, but does not explicitly state that the operation is read-only or disclose any rate limits or side effects. The read-only nature is strongly implied but not confirmed.

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 concise and front-loaded, stating the tool's purpose in the first sentence. The second sentence adds practical usage guidance without unnecessary detail. Every word 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?

Given the tool's simplicity (3 optional parameters, no nested objects, no output schema), the description adequately covers the main purpose and use cases. It could mention pagination limits, but these are already documented in the schema, so the description is sufficiently 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 input schema already provides 100% coverage of parameters with detailed descriptions and examples. The description adds minimal extra meaning beyond mentioning OData filtering and use cases, which is already partially covered in the schema.

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 states 'List Acumatica stock/inventory items' with a specific verb and resource. It distinguishes from the sibling tool 'get_inventory_item' by focusing on listing multiple items and exploring inventory.

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 provides context for use: 'Use this to explore inventory, find items by class or status, or get item lists.' This clearly implies a read-only listing scenario, though it does not explicitly mention alternatives like using 'get_inventory_item' for a single item.

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