autotask_create_company_note

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

The description lacks any behavioral context beyond the basic create operation. It does not disclose side effects, permissions, idempotency, or return value. Since no annotations are provided, the description carries the full burden, which it does not meet.

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 very concise at 6 words, but it lacks structure and front-loading of important information. It is minimal but not wasteful; however, it could be expanded without sacrificing 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 no output schema and no annotations, the description should provide more context about expected behavior, return values, and required permissions. The current description is too sparse for a tool with 4 parameters and a create operation.

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?

All 4 parameters are documented in the input schema with descriptions, achieving 100% coverage. The description adds no extra meaning beyond the schema, so the baseline score of 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 clearly states the verb 'Create' and the resource 'note for a company'. It is unambiguous about the general purpose, but does not differentiate from sibling tools like autotask_create_ticket_note or autotask_create_project_note, which have similar patterns.

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 autotask_create_ticket_note or autotask_search_company_notes. There is no mention of prerequisites, conditions, or exclusions.

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