autotask_create_expense_item

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a creation operation, implying it's a write/mutation tool, but doesn't address critical aspects like required permissions, whether the operation is idempotent, what happens on failure, or what the response looks like. For a mutation tool with 10 parameters and no annotation coverage, this leaves significant behavioral gaps.

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 states exactly what the tool does without any unnecessary words. It's perfectly front-loaded with the core functionality and wastes no space on redundant information. Every word earns its place in this concise formulation.

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 this is a mutation tool with 10 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what happens after creation, what validation occurs, error conditions, or system behavior. The agent would need to guess about important operational aspects despite the tool's complexity.

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 all parameters well-documented in the schema itself. The description doesn't add any parameter-specific information beyond what's already in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description, which applies here.

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 resource ('expense item on an existing expense report'), making the purpose immediately understandable. It distinguishes this from sibling tools like 'autotask_create_expense_report' by specifying it adds items to existing reports rather than creating new reports. However, it doesn't explicitly contrast with other item-creation tools like 'autotask_create_quote_item' or 'autotask_create_ticket_charge'.

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 minimal guidance, only implying usage when you need to add an expense item to an existing report. It doesn't specify when to use this versus creating a new expense report, nor does it mention prerequisites like needing a valid expenseReportId. No explicit alternatives or exclusions are provided, leaving the agent with little contextual direction.

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