bos_loyalty_earn

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

With no annotations, the description carries the full burden of behavioral disclosure. It fails to specify that the tool likely adds points to a customer's loyalty account, whether it is idempotent, or any side effects (e.g., updating balances). This is a critical gap for a write operation.

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 extremely short (3 words), which is concise but at the expense of essential information. It under-specifies the tool's behavior and parameters, making it less useful than a moderately longer but informative description.

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 4 parameters (2 required), no output schema, and no annotations, the description is severely incomplete. It fails to explain parameter purposes, return format, or invocation context, leaving the agent with insufficient information to use the tool correctly.

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, and the description adds no meaning to the four parameters (customer_id, points, order_id, description). The agent must guess what each field represents and how they relate to earning points.

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 'Earn loyalty points' provides a verb and resource, distinguishing it from siblings like bos_loyalty_redeem (redeem) and bos_loyalty_points_balance (balance). However, it lacks specificity on what 'earn' entails (e.g., adding points to a customer account), making it only moderately clear.

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 is given on when to use this tool versus alternatives like bos_loyalty_redeem or bos_loyalty_points_balance. The description does not mention prerequisites, exclusions, or typical use cases, leaving the agent to infer from the name alone.

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