bos_order_show

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

No annotations are provided, so the description carries full behavioral burden. It says 'Get order details', implying a read operation, but does not mention any potential side effects, required permissions, rate limits, or the structure of returned data. More context is needed.

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, clear sentence with no unnecessary words. It is front-loaded with the core action and resource, making it highly efficient.

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 minimally complete for a simple fetch-by-ID operation, but given the absence of an output schema, it would benefit from indicating what 'order details' includes (e.g., items, status, totals) or mentioning error scenarios. Contextual completeness is adequate but not thorough.

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 input schema has 0% description coverage for the single parameter 'order_id'. The description adds only that the order is identified by ID, but does not clarify format, constraints (e.g., length, pattern), or provide examples. The value added is minimal.

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 'Get order details by ID' clearly states the verb (Get), the resource (order details), and the method (by ID). It distinguishes from sibling tools like bos_order_list (list all) and bos_order_search (search with filters) by focusing on a single order retrieval.

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 when a specific order ID is known, but it does not explicitly state when to use this tool versus alternatives like bos_order_list or bos_order_search. No when-not or alternative names are provided.

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