autotask_search_resources

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

With no annotations, the description carries the full burden. It discloses the default page size and pagination behavior, which is helpful. However, it doesn't mention rate limits, authentication, result ordering, or behavior with no matches. Some gaps remain.

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?

Two sentences, front-loaded with core purpose, no wasted words. Very concise and to the point.

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?

The description covers pagination but leaves out other filtering capabilities (isActive, resourceType, searchTerm). No output schema exists to explain return format. For a search tool with 5 parameters, the description is incomplete, though the schema provides some details.

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?

The description only mentions the page parameter, ignoring isActive, searchTerm, resourceType, and pageSize. While the schema has descriptions for three parameters (60% coverage), the description provides minimal added value, failing to compensate for the uncovered parameter semantics.

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 searches for resources (users) in Autotask, with a specific verb and resource. It naturally distinguishes from siblings like autotask_search_companies and autotask_search_services which search different entities.

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?

It mentions default pagination (25 results per page) and suggests using the page parameter, giving basic operational context. It doesn't explicitly state when to use versus alternatives, but the context of searching resources vs other entities is clear from purpose.

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