autotask_search_resources

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

With no annotations, the description carries the burden of behavioral disclosure. It discloses default pagination (25 results per page) and suggests using the page parameter, but lacks details on authentication, rate limits, search behavior (fuzzy/exact), and what fields are searched beyond name/email. Adequate but not thorough.

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 concise at two sentences, with no superfluous information. It front-loads the core purpose and includes essential pagination detail, using brief and clear language.

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?

Despite 5 parameters and no output schema, the description omits critical details such as return format, filtering behavior (isActive, resourceType), ordering, and result interpretation. The minimal information leaves significant gaps for an AI agent to effectively use the tool.

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 60%, but the description adds no additional parameter-level details beyond what's in the schema. It mentions the default page size globally but does not explain undocumented parameters like 'isActive' or 'page.' The description does not compensate for the coverage gap.

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 resources (users) in Autotask,' specifying the purpose and entity (users/resources). It distinguishes from sibling search tools like autotask_search_companies by focusing on resources, and mentions default results per page, adding useful scope details.

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 for finding resources but does not explicitly state when to use this tool over alternatives (e.g., other search tools). No exclusions or context for when not to use are provided, making the guidance implicit rather than explicit.

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