autotask_raw_request

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

Given no annotations, the description effectively discloses key behaviors: automatic header injection (Content-Type, Accept, ApiIntegrationcode, UserName, Secret), path resolution against the zone-resolved base URL, and URL encoding of query parameters. It does not cover error handling or rate limits, but for an escape hatch, this is adequate.

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 concise (5 sentences) and front-loaded with the essential 'escape hatch' concept. Every sentence adds unique information without redundancy.

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?

Considering the tool's nature as an escape hatch and the absence of an output schema, the description covers the input parameter behavior and automatic transformations well. It lacks details on response format, but that is somewhat expected for a raw request tool.

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?

With 100% schema coverage, the description adds value by explaining the automatic header injection, path resolution, and queryParams encoding, which go beyond the schema's basic field descriptions. This enriches the agent's understanding of how parameters interact with the Autotask API.

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 identifies this tool as an escape hatch for unsupported Autotask REST endpoints, distinguishing it from the many typed sibling tools. The phrase 'not yet wrapped by a typed tool' and 'escape hatch' make the purpose 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?

The description advises sparing use and explicitly states that typed tools are preferred for safety, providing clear usage context. It could be strengthened by specifying criteria for when to resort to this raw tool, but the guidance is sufficient.

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