create_ticket_note

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states 'create a note' without revealing whether the note is private, what permissions are needed, whether it triggers notifications, or the shape of the response. This is minimal context beyond the basic action.

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 a single, clear sentence that wastes no words. It front-loads the verb and object, making the core functionality immediately apparent. There is no redundant information or filler.

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?

For a simple tool with two parameters and no annotations, the description is too sparse to be complete. It omits any practical context about note behavior, relationship to ticket conversations, or usage scenarios, leaving the agent to guess important details.

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 0% and the description does not explain either parameter. While 'ticket_id' and 'body' are self-explanatory by name, the description adds no additional meaning (e.g., expected format of body, whether body supports HTML). Parameter semantics are largely left to inference.

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 identifies the action ('Create') and the resource ('a note for a ticket'), so the core purpose is understandable. However, it does not distinguish this tool from sibling tool 'create_ticket_reply', which also creates a comment-like entry on a ticket, so it lacks sibling differentiation.

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?

There is no guidance on when to use this tool versus alternatives like create_ticket_reply. The description conveys a simple action but does not explain the context, such as whether notes are internal-only, or when a note is appropriate.

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