autotask_search_service_bundles

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only says 'Search for service bundles with optional filters'—no mention of read-only nature, pagination (though pageSize is in schema), or output format. Minimal transparency beyond the name.

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 very short (one sentence), which is concise but omits necessary details like result format or usage context. It is not front-loaded with key behavioral 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?

Given no output schema and siblings like 'autotask_get_service_bundle', the description is incomplete. It fails to clarify that the tool returns a list, does not hint at response structure, and does not address typical usage scenarios.

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 67% (searchTerm, pageSize described; isActive lacks description). The description adds no extra meaning for parameters—just 'optional filters'. It does not explain search behavior (e.g., partial match) or the role of isActive.

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 the resource 'service bundles', which distinguishes it from sibling tools like 'autotask_get_service_bundle' (single retrieval) and other search tools (e.g., 'autotask_search_services'). However, it does not explicitly note the distinction or mention that it returns multiple results.

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?

No guidance on when to use this tool versus alternatives (e.g., 'autotask_get_service_bundle' for a specific bundle). No context on prerequisites, limitations, 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.