autotask_search_resources

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

No annotations provided, so description carries full burden. Discloses default 25 results per page and pagination support. However, lacks details on read-only nature, rate limits, or behavior with empty search term. Adds some value but insufficient for complete 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?

Two concise sentences. Front-loaded with purpose, followed by key behavioral detail (default page size). No filler or redundant information.

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?

Complexity is moderate (5 parameters, no required, no output schema). Description fails to cover return value structure or field details. Omits any prerequisites or edge cases. Incomplete for an agent to fully understand without additional context.

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% (3 out of 5 parameters described). Description reinforces 'searchTerm' purpose and introduces pagination via 'page', but adds no new meaning for 'isActive' or 'resourceType'. Meets baseline but does not compensate for missing schema descriptions.

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?

Clearly states the tool searches for resources (users) in Autotask. The verb 'search' and resource 'resources' are specific. Distinguishes from sibling search tools (e.g., companies, contacts) by focusing on resources.

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?

Implies usage for searching resources but provides no explicit guidance on when to use this tool vs alternatives. No 'when not to use' or references to other tools. The description assumes the agent knows the sibling context.

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