autotask_search_resources

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

Mentions it returns 25 results per page and pagination behavior. No annotations provided, so description partially covers behavioral aspects but does not mention rate limits, authentication, or potential errors. Adequate but not comprehensive.

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, clear and to the point. Front-loads the main purpose. Could be slightly more structured but no wasted words.

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, description adequately covers pagination but lacks details on what is returned (e.g., just names or full profiles). Could be improved with return info.

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 100% with descriptions, so description adds little beyond repetition of defaults and page parameter. Baseline 3 is appropriate since description does not add significant semantics beyond 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?

States it searches for resources (users) in Autotask. Verb 'search' and resource 'resources' are specific. However, does not explicitly differentiate from sibling search tools like autotask_search_contacts, though the resource type is implied.

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?

Provides default page size and pagination info, but no guidance on when to use vs alternatives like autotask_search_contacts or autotask_search_companies. No when-not-to-use or preference for resource search.

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