autotask_search_service_bundles

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

No annotations are provided, so the description must fully disclose behavioral traits. However, it does not mention whether the operation is read-only, any default filtering (e.g., active bundles only), pagination behavior, authorization requirements, or rate limits. This leaves significant ambiguity for the AI agent.

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 one sentence with 6 words, making it extremely concise and front-loaded with the key action and resource. However, it could benefit from slightly more detail without becoming verbose.

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 three parameters, no output schema, and no annotations, the description is insufficient. It does not explain the search mechanism (e.g., exact match vs fuzzy), default behavior, response format, or any constraints. An agent lacks necessary context to use the tool correctly.

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 description coverage is 67% (two of three parameters have descriptions), but the description adds no additional meaning beyond 'optional filters'. The 'isActive' parameter lacks a description in both schema and description, and the description does not explain how parameters interact or default values.

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 the verb 'Search' and resource 'service bundles', and includes 'with optional filters' to indicate flexibility. It distinguishes from siblings like autotask_get_service_bundle (retrieve by ID) and autotask_create_* (creation tools).

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 provides no guidance on when to use this tool versus alternatives such as autotask_search_services or autotask_get_service_bundle. It does not mention prerequisites, preferred scenarios, or when not to use it.

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