autotask_search_service_call_ticket_resources

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

With no annotations, the description carries full burden for behavioral disclosure. It only states 'search' which implies read-only, but does not disclose any additional behavioral traits such as authentication requirements, rate limits, or whether the operation is safe beyond what the name suggests.

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 one sentence, direct, and front-loaded with the core action. However, it could be slightly more informative without losing 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?

For a simple search tool with three documented parameters and no output schema or nested objects, the description is minimally adequate. It does not clarify return value structure or pagination behavior beyond pageSize, leaving some ambiguity 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 description coverage is 100% (all three parameters have descriptions). The tool description adds no extra meaning beyond the schema, which already explains that resourceId filters by technician ID, serviceCallTicketId by ticket ID, and pageSize controls result count. Baseline 3 is appropriate.

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 resource (technician) assignments on service call tickets.' It uses a specific verb ('search') and identifies the resource ('resource assignments') and context ('service call tickets'), differentiating it from sibling tools like autotask_search_service_call_tickets which search for tickets themselves.

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 the use case (finding technician assignments) but does not explicitly state when to use this tool versus alternatives like autotask_create_service_call_ticket_resource. No when-not-to-use guidance is provided.

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