autotask_raw_request

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

The description discloses automatic header addition, base URL resolution, and query parameter encoding. However, it lacks details on potential error responses or consequences of invalid paths, which would be useful.

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 extremely concise with two sentences, immediately stating purpose and usage preference, with 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?

Given the tool's nature as a raw request handler, the description covers key aspects. Lack of output schema note is acceptable as return value depends on the API call; however, a brief note about response format could improve completeness.

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?

The schema already provides full coverage, and the description adds value by explaining queryParams handling (flat objects, URL-encoded) and path resolution, enhancing understanding beyond the schema.

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 defines the tool as an escape hatch for Autotask REST endpoints not yet wrapped, and distinguishes it from the many typed tools listed as siblings.

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 explicitly states 'Use sparingly — typed tools are preferred for safety', providing clear guidance on when to use this tool versus alternatives.

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