BC_List_Items

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

No annotations are present, and the description only hints at filtering and pagination behavior without detailing return structure, rate limits, or default behavior (e.g., whether it returns all items if no filter).

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 a single sentence, which is concise but omits essential details that could be added without significantly increasing length.

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?

With 4 parameters, no parameter descriptions, an output schema not explained, and no usage guidelines, the description is incomplete for effective tool invocation.

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 0% and the description only vaguely mentions 'filtering and pagination', failing to explain the 'resource' parameter values, filter syntax, or semantics of 'top' and 'skip'.

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 retrieves items from Business Central with filtering and pagination, distinguishing it from sibling tools that create, delete, update, or retrieve single items by field.

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 implies use for listing with filtering/pagination but does not explicitly differentiate from BC_Get_Items_By_Field or specify when not 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.