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 indicate a read-only operation via 'Get' and mentions filtering/pagination (behavioral capabilities), but it doesn't disclose response format, default pagination limits, or any potential side effects. This is a minimal but sufficient disclosure for a simple list operation.

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, efficient sentence that gets straight to the point. No filler or redundant content; it perfectly balances brevity with essential information.

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 simple list tool with fully documented parameters, the description is adequate. However, it lacks context on when to use the tool versus siblings, and does not mention anything about the return value or response structure (though no output schema exists). It is a minimally complete description for a basic operation.

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 schema has full descriptions for all 4 parameters (100% coverage), so the baseline is 3. The description's mention of 'filtering and pagination' aligns with the 'filter', 'top', and 'skip' parameters but adds no new semantic detail beyond what the schema already provides.

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 uses the specific verb 'Get' with the resource 'items from Business Central' and mentions filtering and pagination capabilities. It clearly states what the tool does, but it does not differentiate itself from the sibling tool 'get_items_by_field', which likely performs a similar retrieval function in a different manner.

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 no explicit guidance on when to use this tool versus alternatives like 'get_items_by_field' or 'get_schema'. The mention of filtering and pagination implies a use case, but there is no direct statement of context, prerequisites, or exclusion criteria.

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