autotask_update_contract

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

No annotations present; description discloses it's a PATCH operation (non-destructive) and that non-provided fields remain unchanged. Does not address permissions, rate limits, validation, or response details. Adequate but incomplete.

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 sentences, front-loaded with action and method, followed by key usage tip and enum. No redundant 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?

For a 32-parameter tool with no output schema or annotations, the description is minimal but covers core purpose and key usage. Lacks examples, error info, and permission hints, which would be beneficial given 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 coverage is 100% with good parameter descriptions. Description adds value by clarifying the PATCH partial update pattern and providing status enumeration (1=In Effect, 0=Inactive). Exceeds baseline of 3.

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?

Description clearly states the tool updates an existing contract using PATCH, distinguishes from sibling update tools by specifying 'Contract' and partial update behavior. The verb 'update' and method 'PATCH' are explicit.

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 guidance to pass only fields to change and notes id is required. Gives status enum mapping. However, lacks explicit when-not-to-use or alternative tool references, but sibling entities provide implicit distinction.

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