autotask_get_company_note

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

No annotations are provided, so the description must convey behavioral traits. It only states 'Get', implying a read operation, but omits details like required permissions, whether the note is returned fully or partially, or any side effects. With no annotations and no additional context, the behavioral transparency is insufficient.

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 with no fluff. While it is minimal, it is appropriately sized for a straightforward retrieval tool, though it could be slightly expanded without harming conciseness.

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 lack of an output schema and the presence of sibling get tools (e.g., 'autotask_get_ticket_note'), the description does not help the agent understand what fields or structure the response will have. For a simple get operation, more context about the returned note fields would improve 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?

Schema coverage is 100% with both 'companyId' and 'noteId' already described clearly in the input schema. The description adds no extra meaning beyond what the schema provides, meeting the baseline expectation for a tool with high schema coverage.

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 ('Get'), the resource ('specific company note'), and the identifying criteria ('by company ID and note ID'). It effectively distinguishes this tool from siblings like 'autotask_search_company_notes' (which lists multiple) and 'autotask_create_company_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 provides no explicit guidance on when to use this tool versus alternatives, such as 'autotask_search_company_notes' for searching or other get tools for different entities. It lacks context on prerequisites or situations where this tool is preferred.

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