List items

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention pagination behavior, default limits, or the return format, although top/skip schema descriptions hint at paging. The description only provides parameter semantics without deeper behavioral context.

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 two concise sentences: the first states the purpose, the second gives parameter usage guidance. Every word earns its place, with no redundancy or fluff.

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 covers the core purpose and parameter usage well, but lacks details on return values and behavioral traits like pagination or default limits. Since there is no output schema, the description should at least mention what is returned, but it only implies a list of inventory items.

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?

Schema coverage is 100%, so the baseline is 3. The description adds practical guidance by explaining that `search` performs a substring match on displayName (already in schema) and providing a concrete OData filter example (`inventory lt 10`), which enriches the schema's bare description.

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 the tool lists inventory items in the working company, using the specific verb 'List' and resource 'inventory items'. This distinguishes it from sibling tools that list other entities (companies, customers, sales orders).

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 clear guidance on how to use the parameters: use `search` for substring match and `filter` for OData filtering with an example. However, it does not explicitly compare against alternatives like bc_query or other list tools, though the purpose clearly delineates when to use this tool.

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