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

With all annotation hints false, the description carries the burden and does well: it discloses server-side provenance stamping and non-spoofability, clarifies that session/workflow ids are opaque metadata links, and states the constraint that new epics cannot be created as done. This goes well beyond the boolean annotations and adds meaningful behavioral context, though it omits side effects like notifications or validation errors.

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 compact at four sentences, front-loaded with the primary action, and every sentence adds value—provenance, opaque IDs, and the epic constraint. It earns its length given the tool's complexity, though a slightly tighter phrasing of the effort/action_type sentence could improve it.

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 an output schema and 15 parameters with a nested external_ref, the description provides solid operational context: creation scope, subticket support, effort/action_type guidance, provenance, ID semantics, and a creation constraint. It does not cover all parameters or potential error behavior, but for a create tool with an output schema, it is reasonably complete.

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 description coverage is only 20%, so the description must compensate. It adds useful semantics for effort (degree of difficulty), action_type (kind of work), parent_id (subticket creation), and session/workflow ids (opaque metadata). However, many other parameters (labels, priority, order_index, external_ref, etc.) are left to self-evident naming or the sparse schema, leaving gaps for a 15-parameter tool.

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 opens with a specific verb+resource: "Create a ticket on the caller's board," and immediately distinguishes itself from sibling tools like ticket_batch_create (single vs batch) and ticket_update (creation vs modification). The optional parent_id subticket behavior adds precise scope. This is unambiguous and fully distinguishes the tool.

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 implies when to use the tool (when creating a single ticket) and explains the optional subticket capability, giving clear context. However, it does not explicitly mention alternatives (e.g., ticket_batch_create for bulk creation) or provide when-not-to-use guidance, so it stops short of a full 5.

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