autotask_search_resources

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It reveals the default page size and pagination control, but lacks information about whether searches are exact or fuzzy, what happens with empty searchTerm, authorization requirements, or rate limits. This is moderate transparency.

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 two sentences, front-loading the purpose and adding a critical pagination detail. Every sentence is efficient and adds necessary information without redundancy.

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 5 parameters, no output schema, and no annotations, the description covers the core purpose and pagination default. However, it lacks details on how to use parameters like 'isActive' and 'resourceType' effectively, and does not describe the return structure or fields. It is minimally adequate.

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 input schema covers 60% of parameters with descriptions. The description adds value by specifying the default page size (25) and advising to use page for more results. However, it does not elaborate on the 'isActive' parameter or provide additional meaning beyond the schema for other parameters.

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 resources (users) in Autotask', providing a clear verb and resource. Among sibling search tools (autotask_search_companies, autotask_search_tickets, etc.), it distinguishes itself by specifying 'resources (users)'.

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 mentions that results are 25 per page and that the page parameter can be used for more, offering some contextual guidance. However, it does not explicitly state when to use this tool versus other search tools (e.g., searching for companies or tickets), nor does it provide alternatives or conditions.

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