bos_promotion_show

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Get promotion details', implying a read operation, but does not disclose error handling, return format, or any prerequisites (e.g., whether the promotion must exist).

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 three-word description is concise but under-specified. It communicates the core purpose but misses additional context that could fit without becoming 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's simplicity (one param, no output schema), the description is insufficient. It does not describe the return value, so an agent cannot fully understand what to expect from the tool 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?

Schema description coverage is 0%, and the description does not mention the 'promotion_id' parameter or its role. Adding context like 'Provide the promotion ID to retrieve details' would significantly improve parameter semantics.

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 promotion details' clearly states the action and resource, distinguishing it from sibling tools like bos_promotion_list (which lists promotions) and bos_promotion_apply (which applies a promotion). However, it lacks specificity about what 'details' entail.

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 alternatives is provided. For example, it does not mention that this is for retrieving a single promotion by ID, while bos_promotion_list is for listing all promotions.

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