autotask_search_service_calls

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

With no annotations, the description must carry the behavioral disclosure burden. It states 'Search' which implies a read operation, but does not confirm readonly behavior. It also does not mention pagination (though pageSize parameter exists), results format, error handling, or authorization requirements. This is insufficient for a full understanding.

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, efficient sentence with no wasted words. It is front-loaded with the main purpose. However, it could be slightly expanded (e.g., mention pagination) without becoming verbose, so it's not a perfect 5.

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 has 5 optional parameters and no output schema, the description is too brief. It does not explain what a service call is, that results are a list, or how pagination works. For a search tool in a complex domain with many siblings, more context is needed to select and use it correctly.

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%, so baseline is 3. The description adds no new meaning beyond listing filter categories; it merely summarizes the parameters. It does not provide usage examples or clarify parameter relationships, so it adds minimal value.

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 'Search for service calls in Autotask', which is a specific verb and resource. It mentions filtering options, distinguishing it from get_service_call (single record) and other search tools. However, it does not explicitly differentiate from siblings like autotask_search_service_call_tickets, which could overlap.

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 implies usage when filtering by company, status, or date range, but provides no guidance on when not to use it. For example, it does not mention that for a single known service call ID, autotask_get_service_call would be appropriate. No prerequisites or exclusions are stated.

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