post_delivery_tip

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

No annotations are provided, so the description must fully disclose behavior. It only states 'add or update' without mentioning idempotency, side effects, authentication needs, or other safety details. This is insufficient for a mutation tool.

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 short and includes a structured Args section. It is clear without unnecessary words, though it could be slightly more concise by combining lines.

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?

The description covers the basic operation but lacks details on return values or error conditions, even though an output schema exists. For a simple tool, it is adequate but could provide more 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?

With 0% schema coverage, the description adds brief parameter explanations: 'order_id: The order ID' and 'tip_amount: Tip amount in dollars.' The unit clarification ('in dollars') is helpful, but the descriptions are minimal.

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 'add or update the tip after delivery,' specifying the resource (tip), action (add/update), and context (after delivery). It distinguishes from siblings like 'set_tip' by implication, but does not explicitly contrast.

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 indicates when to use ('after delivery'), but provides no exclusions or explicit guidance on when not to use it, nor does it reference alternatives like 'set_tip' for pre-delivery tips.

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