autotask_create_ticket_note

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

With no annotations, the description bears full responsibility for behavioral disclosure. It only states 'Create a new note', implying a write operation, but fails to mention auth needs, side effects, error conditions, or idempotency. The agent has no insight into the tool's behavior beyond mutation.

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, concise sentence that is front-loaded with the core action. It could be more informative without being verbose, but it avoids redundancy given the schema covers the parameters.

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?

Lacking an output schema, the description should at least indicate what the tool returns (e.g., the note ID) or confirm success. It provides no such information. Additionally, it does not help the agent decide when to use this tool among many similar create tools, leaving gaps in contextual completeness.

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 input schema provides 100% description coverage, with detailed explanations for noteType and publish fields. The tool description itself adds no extra meaning beyond what is already in the schema, so it meets the baseline without enhancement.

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 action (create) and resource (note for a ticket), which distinguishes it from other create tools like autotask_create_ticket or autotask_create_company_note. However, it does not explicitly differentiate from similar note-creation tools (e.g., autotask_create_project_note), leaving some ambiguity.

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?

No guidance is provided on when to use this tool versus alternatives, such as when to add a note to a ticket vs. creating a separate ticket. No prerequisites or conditions are mentioned, limiting the tool's usability for an AI agent.

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