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 disclose behavioral traits. It only states it is a 'Get' operation, implying read-only behavior, but does not mention idempotency, required permissions, rate limits, or what happens if the note does not exist (error vs. null response). This lack of detail hinders correct invocation.

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 of 9 words with no fluff. However, it is slightly under-specified for behavioral and usage aspects. It earns a high score for conciseness but loses a point for sacrificing necessary context.

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 retrieval tool with two parameters and no output schema, the description is largely adequate to understand what the tool does. However, it lacks completeness in usage guidance and behavioral transparency. A more complete description would mention that the tool returns a single note object and that the note ID must correspond to a note associated with the given company.

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 100% coverage. The description adds 'by company ID and note ID', which reiterates the schema but does not provide additional semantic context such as data types, validation rules, or examples. Baseline of 3 is appropriate since the schema does the heavy lifting.

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 explicitly states it retrieves a specific company note using two identifiers (company ID and note ID). This clearly distinguishes it from sibling tools like 'autotask_search_company_notes' (searches for notes) and 'autotask_create_company_note' (creates a note). The verb 'Get' and the resource 'company note' are specific and unambiguous.

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 guidance on when to use this tool versus alternatives. It does not mention that 'autotask_search_company_notes' should be used first to find the note ID, nor does it state when not to use it (e.g., if the note does not exist). No prerequisites or context for invocation are given.

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