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

Annotations only declare readOnly=false, destructive=false, idempotent=false; the description adds the non-obvious trait that the tool is batch-limited to 10 items and must be called repeatedly for larger sets. That is genuine behavioral context beyond the structured fields. It stops short of covering partial-failure or duplicate-handling behavior, which matters for a non-idempotent write.

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?

Two short sentences with zero filler, front-loading the core action and then the batching constraint an agent must respect. Nothing could be removed without losing information.

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?

An output schema exists so return values need no explanation, and the critical batching loop is documented. Remaining gaps are minor but real: the relationship between addons and ticket_type_ids, and what happens if a mid-batch call fails, are left to inference.

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 coverage is 100% at the top level, so the schema carries the parameter documentation and baseline 3 applies. The description adds only the 10-item batching constraint (already mirrored in the addons schema description) and says nothing about nested fields such as amount, quantity, is_enabled, or ticket_type_ids.

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?

States a specific verb and resource ("Create ticket addons") plus scope ("in the provided event"), which is far more informative than the bare title. It distinguishes itself from update_addon/delete_addon by naming the create action, though it never explicitly contrasts with those siblings.

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 gives a procedure for the >10 case, which implies when and how to call repeatedly, but it never states prerequisites (event must exist, permissions) or when to prefer update_addon over re-creating. Usage is implied rather than spelled out.

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