bos_customer_show

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

No annotations are provided, and the description does not disclose behavioral traits such as read-only nature, authentication requirements, or behavior when the customer ID does not exist. The minimal description relies entirely on the tool's name.

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 of five words, front-loading the key purpose. It is efficient and avoids unnecessary detail, but may be too concise for adequate guidance.

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 no output schema, the description does not specify what 'customer details' include (e.g., name, email, address). It also lacks information on error handling or edge cases, leaving the agent with incomplete context for 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?

The input schema has 0% description coverage for its single parameter 'customer_id'. The description does not add any meaning beyond the parameter name, such as expected format or example values.

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 customer details by ID' clearly states the action (get details) and the resource (customer) with an ID parameter. It distinguishes from list/search tools by implying retrieval of a single entity, but does not explicitly differentiate from siblings like bos_customer_show vs. bos_customer_orders.

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 guidance on when to use this tool versus other customer-related tools (e.g., bos_customer_list, bos_customer_search). The description lacks explicit context for use cases or alternatives.

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