list_business_partners

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

With no annotations, the description carries the full burden and does add useful context by mentioning OData capabilities and the category code mapping. However, it does not disclose authentication requirements, default/return behavior, or potential errors, which is a notable gap for a tool with no annotation coverage.

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?

Three sentences with no filler: the purpose, OData capabilities, and category mapping are front-loaded, and the filter example is practical. It is concise while each sentence contributes useful 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?

The description is reasonably complete for a list operation: purpose, OData capabilities, and an example are present, and parameter details live in the schema. Still, without an output schema or annotations, it leaves return-shape details and pagination defaults unaddressed, and it doesn't point to get_business_partner for singular lookups.

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 already covers all 6 parameters, providing a baseline of 3. The description goes beyond by explaining that category '1' means Person and '2' means Organization and giving a concrete $filter example with substringof, which adds genuine semantic value.

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 business partners from SAP S/4HANA and highlights OData filtering, sorting, pagination, and field selection. While the verb 'List' distinguishes it from the sibling 'get_business_partner', there is no explicit contrast naming that sibling, so it stops short of full differentiation.

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?

No explicit guidance is given on when to use this tool versus get_business_partner. The only usage hint, using $filter for search, is a how-to rather than a tool-selection criterion, leaving the agent to infer the appropriate context.

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