autotask_create_company_note

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

With no annotations provided, the description only implies a write operation ('Create') but fails to disclose side effects, permissions required, or error handling (e.g., invalid companyId). Basic behavioral traits are missing.

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, front-loading the purpose. While very brief, it contains no filler and is easily parsed.

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 no output schema and no annotations, the description provides minimal context. It defines the action and target but omits return value (e.g., created note ID) and behavioral details, leaving gaps for a simple creation tool.

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 covers all 4 parameters with descriptions, achieving 100% coverage. The tool description adds no additional meaning beyond the schema, so it meets the baseline of 3.

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 'Create a new note for a company' clearly states the action (create) and the specific resource (company note), distinguishing it from other note creation tools like autotask_create_ticket_note or autotask_create_project_note. However, it could be more explicit about attaching it to a company entity.

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 such as autotask_search_company_notes (for reading) or autotask_create_ticket_note (for different entities). It lacks context about prerequisites or preferred use cases.

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