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

Beyond the annotations (destructiveHint, readOnlyHint), the description adds behavioral context: 'Sent messages cannot be recalled' and 'Updates can replace assignments, tags and metadata.' This warns about irreversible actions and replacement semantics, which is valuable for agents.

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 concise and well-structured, consisting of three short sentences that capture the core functionality, additional capabilities, and a warning. No redundant or vague language is present.

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 11 parameters and nested objects, the description provides sufficient context by outlining the primary operations (create/update) and side effects. It does not explain output or error handling, but the absence of an output schema lowers the need for that detail.

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 does not add parameter-level details; it relies on the schema descriptions, which are already comprehensive (100% coverage). Since the schema covers all parameters with meaningful descriptions, the baseline is appropriate.

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's purpose: 'Create or update support tickets.' It distinguishes itself from related tools like ticket-read and ticket-message-write by focusing on ticket creation/update and mentioning the first client message. The additional note about messages not being recalled reinforces the scope.

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 usage for creating or updating tickets but does not explicitly compare to alternatives. It does not mention when to use ticket-message-write for subsequent messages or ticket-read for viewing tickets. While the intent is clear, explicit guidance would improve selection.

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