autotask_raw_request

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

Discloses automatic addition of headers, base URL resolution, and query parameter encoding. However, lacks information on response format or error handling, which would be helpful given no annotations or output schema.

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?

Three sentences, front-loaded with purpose. Efficient but could benefit from a list for clarity. No unnecessary 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?

Covers all four parameters with usage guidance but omits response format and error scenarios. Given the lack of output schema and annotations, additional details would 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?

Adds value beyond schema by explaining queryParams are a flat object of specific types and URL-encoded, and that path is relative to a base URL. Body and method are covered adequately.

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 it's an 'escape hatch' for unsupported Autotask REST endpoints, distinguishing it from typed sibling tools. The verb 'escape hatch' and mention of 'raw request' 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?

Explicitly says 'Use sparingly — typed tools are preferred for safety.' Provides context on automatic headers, path resolution, and query parameter handling, guiding when to use this tool over alternatives.

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