autotask_get_ticket_note

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

No annotations are provided, so the description carries the full burden. The verb 'Get' implies a read-only operation with no side effects, which is acceptable for a retrieval tool. However, it does not explicitly state that it is non-destructive or require special permissions, leaving some implicit assumptions.

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 sentence that is front-loaded with the action and resource. It contains no extraneous information and is highly efficient.

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?

The tool has no output schema, so the description should provide some indication of the return value. It does not describe the response shape or handling of errors (e.g., if the note does not exist). For a simple get operation, this is minimally adequate but could be improved.

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 already describes both parameters with clear descriptions: 'The note ID to retrieve' and 'The ticket ID'. The description adds no additional meaning beyond what the schema provides, which is sufficient. Schema coverage is 100%, so baseline 3 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 'Get a specific ticket note by ticket ID and note ID' clearly specifies the action (get), the resource (specific ticket note), and the identifiers (ticket ID and note ID). It differentiates from siblings like autotask_search_ticket_notes which retrieves multiple notes, and autotask_create_ticket_note which creates.

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 when you have a specific note ID and ticket ID. It does not explicitly state when not to use it or mention alternatives, but the context is clear: use this to retrieve a single note, not to search or create. The sibling tools for searching and creating provide clear alternatives.

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