autotask_update_company

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

No annotations are provided, so the description must fully convey behavioral traits. It says 'update' implying mutation but does not disclose idempotency, partial update behavior (only specified fields are updated), auth requirements, or what happens if id is invalid. This is insufficient for a mutation tool.

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 that conveys the essential purpose. It is concise and front-loaded, but could be slightly expanded to include key behavioral details without becoming verbose.

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 annotations and output schema, the description is too brief. It does not explain return values (e.g., whether it returns the updated company or just success), error handling, or which fields are required beyond id. The tool has 8 parameters with 100% schema coverage, but completeness is low due to missing behavioral and usage context.

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%, so the description adds no extra parameter info. Baseline 3 is appropriate. The tool updates company fields, but the description does not clarify how overlapping fields behave (e.g., if companyName is omitted, does it remain unchanged?).

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 'Update an existing company in Autotask', which identifies the verb (update), resource (company), and system (Autotask). It distinguishes from sibling tools like autotask_create_company, but could be more specific about which fields are updatable.

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 vs alternatives like autotask_update_company_site_configuration or create_company. There is no mention of prerequisites (e.g., company must exist) or when not to use it.

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