postCustomerPoints

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

The description explains the additive behavior (points added to current balance, negative for subtraction) and that the new balance is returned. Annotations indicate readOnlyHint=false and destructiveHint=true, which align with the mutation described. No contradiction.

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 three concise sentences, front-loading the core action, then parameter details, then sibling differentiation. No extraneous content.

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?

For a simple mutation tool with two required parameters and no output schema, the description fully explains operation, parameters, effect, and alternatives. No gaps.

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 description provides full semantics for both parameters: customer_id selects target, points is integer for addition (negative for subtraction). This compensates for the schema's 50% description coverage.

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 clearly states the tool adds or subtracts shop points for a specified customer, using customer_id and points. It distinguishes from siblings like getCustomer, updateCustomers, and updateCustomerMembership.

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 provides explicit guidance: use for point adjustment, and names alternative tools for other customer operations (getCustomer, updateCustomers, updateCustomerMembership).

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