postCustomerPoints

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

Annotations already indicate destructiveHint=true. Description adds that balance is added to current value and new balance is returned, which is helpful. No contradiction or missing critical behavior.

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?

Few sentences, front-loaded with purpose, then usage, then alternatives. Every sentence adds value; no redundancy.

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?

Tool is simple (2 required params, no output schema). Description fully covers input, behavior, and output (new balance returned). No gaps given the context.

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 covers only 50% of parameters with descriptions (points). Description compensates by explaining both customer_id (identifies customer) and points (integer to add/subtract), adding meaning beyond schema.

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?

Description clearly states the verb (add/subtract) and resource (customer points). It explicitly differentiates from siblings like getCustomer, updateCustomers, and updateCustomerMembership by noting their respective purposes.

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?

Describes how to use each parameter (customer_id and points) and when to use alternatives (getCustomer for retrieval, updateCustomers for info update, updateCustomerMembership for rank change). Provides explicit guidance on negative values for subtraction.

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