autotask_search_services

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

Absent annotations, the description fails to disclose behavioral traits such as pagination, authentication needs, rate limits, or behavior when no results are found. It only states 'search' and 'optional filters', leaving significant gaps.

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 concise sentence with no wasted words. It is front-loaded with the core purpose. However, it may be too brief, missing opportunities to include useful details without sacrificing 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?

Given the lack of output schema and moderate complexity (3 optional parameters), the description is incomplete. It does not explain what results are returned, pagination behavior, or how services are defined, failing to provide a complete understanding for the agent.

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 67% (two of three parameters have descriptions). The tool description adds no meaning beyond the schema; it does not explain 'isActive' (missing description) or provide additional context for 'pageSize' and 'searchTerm'.

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 searches for services with optional filters. The verb 'search' and resource 'services' are specific, but it does not differentiate from sibling search tools (e.g., autotask_search_companies) which also search for different resources.

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?

No guidance on when to use this tool versus alternatives. Sibling tools include many other search tools, but the description provides no criteria for choosing this one. No mention of when not to use or prerequisites.

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