autotask_search_service_calls

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

The description only states 'Search' and 'Filter by...' but provides no behavioral details such as pagination (though pageSize parameter exists), result ordering, or that it returns a list of service calls. With no annotations, the description carries full burden and falls short.

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 sentence that efficiently communicates the tool's purpose and filter capabilities. It is front-loaded with the core action ('Search for service calls') and includes key filtering hints. No waste.

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 parameters, no output schema, and no annotations, the description is insufficient. It fails to explain that all parameters are optional, what the default behavior is (e.g., all service calls if no filters), or the nature of the response (list vs single). More context is needed for effective use.

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 description coverage is 100%, so the parameters are well-documented. The description adds little new meaning beyond summarizing the filters ('company, status, or date range'). Baseline score of 3 is appropriate as the description does not enhance clarity 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 explicitly states 'Search for service calls in Autotask', clearly indicating a search operation. It also lists filter options, distinguishing it from sibling tools like autotask_get_service_call (single record retrieval) and autotask_create_service_call (creation).

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. For example, it doesn't mention that for retrieving a single known service call, autotask_get_service_call is more appropriate. The description lacks any when-to-use or when-not-to-use instructions.

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