Settlement_detail

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It only says 'getting,' implying a read operation, but does not mention safety, authentication, rate limits, or what happens if the order doesn't exist. More detail is needed for a reliable agent invocation.

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 very short with no unnecessary words, but the phrase 'An API for' is filler. The core verb+object 'getting a settlement detail' is clear but could be more direct. Overall, it earns its place without being verbose.

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 has a single parameter and an output schema (not shown), the description is adequate but lacks explanation of what a settlement detail is and when to use it. For a simple tool, it is minimally complete but could be improved with brief context on the returned data or purpose.

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% for the single parameter orderNo, which is described as 'Order number.' The description adds no additional meaning beyond the schema, so baseline score of 3 is appropriate.

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 states 'getting a settlement detail,' which is a specific verb and resource, but it is vague about what a 'settlement detail' entails. The connection to the order number parameter is implied but not explicit, leaving room for ambiguity. It does not distinguish itself well from sibling tools like Order_detail.

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?

There is no guidance on when to use this tool versus alternatives. Sibling tools include Order_detail and others, but the description provides no context for when Settlement_detail is appropriate, such as for financial settlement data after an order is completed.

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