autotask_create_service_call_ticket_resource

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Assign a resource' which implies a write/mutation operation, but fails to disclose critical traits such as required permissions, whether the assignment is reversible, potential side effects (e.g., notifications), or error conditions (e.g., if the resource is already assigned). This leaves significant gaps for a mutation tool with zero annotation coverage.

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, efficient sentence that directly states the tool's purpose without any fluff or redundant information. It is front-loaded and wastes no words, making it easy for an agent to parse quickly. Every part of the sentence earns its place by clarifying the action and target.

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 mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral aspects (e.g., permissions, side effects), usage context, and what the tool returns upon success or failure. While the schema covers parameters well, the overall context for safe and effective use is insufficient, especially given the tool's potential impact on system state.

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 description coverage is 100%, with clear descriptions for all three parameters in the input schema. The description adds no additional semantic context beyond what the schema already provides (e.g., it doesn't explain what a 'roleID' entails or provide examples). Given the high schema coverage, the baseline score of 3 is appropriate as the schema handles the heavy lifting without extra value from the description.

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 action ('Assign') and target ('a resource (technician) to a service call ticket'), making the purpose immediately understandable. It distinguishes itself from sibling tools like 'autotask_create_service_call_ticket' or 'autotask_delete_service_call_ticket_resource' by focusing on assignment rather than creation or deletion. However, it doesn't explicitly differentiate from other assignment-related tools in the list, keeping it from a perfect score.

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_update_service_call' or 'autotask_search_service_call_ticket_resources', nor does it mention prerequisites like needing an existing ticket or resource. It lacks explicit when-to-use or when-not-to-use instructions, leaving the agent to infer context from the tool name alone.

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