autotask_update_project

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

States 'Only the fields you provide will be updated,' disclosing partial update behavior. However, with no annotations, it does not cover other traits like permissions, reversibility, or error handling.

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?

Two efficient sentences, front-loaded with purpose and partial update behavior, then a concrete example. No wasted words.

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?

Adequately covers behavior and a use case, but with 12 parameters and no output schema, it could mention return format or side effects. Not fully complete.

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?

Adds value beyond the schema by noting the common use case for status and the required relationship between assignedResourceID and assignedResourceRoleID. Schema already has rich descriptions (100% 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?

Clearly states verb 'update', resource 'existing project', and includes a common use case (status=5 to mark Complete). Distinguishes from sibling tools like autotask_create_project and autotask_search_projects.

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?

Provides a common use case but no explicit guidance on when to use vs alternatives or when not to use. Lacks exclusion criteria and prerequisites.

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