autotask_create_opportunity

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

No annotations are provided, so the description must carry the full burden. It only states 'Create a new sales opportunity' with no disclosure of side effects (e.g., default values, required permissions, idempotency, or what happens when mandatory fields are missing). For a creation tool, this is insufficient.

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 sentence of 7 words, no filler. It is front-loaded with the action and resource. However, it could benefit from adding one more sentence to improve completeness without harming 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?

Despite 15 parameters and no output schema, the description does not explain how to obtain picklist IDs (stage, opportunityCategoryID), default behaviors (useQuoteTotals, amount), or what the API returns. Given the complexity and number of sibling tools, more context is needed.

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% with clear descriptions for each parameter. The tool description does not add meaning beyond the schema (e.g., no hints about valid values for stage beyond referencing autotask_get_field_info). 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 uses a specific verb 'Create' and resource 'new sales opportunity' with system 'Autotask', clearly distinguishing it from siblings like autotask_create_company or autotask_create_ticket. It directly states what the tool does.

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, no prerequisites (e.g., need for company, contact), no exclusions, and no mention of related tools like autotask_search_opportunities or autotask_get_field_info for picklist values.

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