autotask_search_billing_item_approval_levels

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It only mentions a 'search' action without detailing pagination behavior, rate limits, or any side effects. The schema's pagination parameters are not referenced, and the tool's read-only nature is assumed but not stated.

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 extremely concise: two sentences with the action front-loaded. Every word adds value, and there is no redundancy. It achieves clarity without verbosity.

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 7 parameters, the description is adequate but lacking: it does not describe the returned data structure or whether results are paginated. For a search tool, an agent would benefit from knowing the typical output fields or how approval levels relate to other entities.

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 high (86%), so the baseline is 3. The description adds no additional meaning beyond the schema—it does not explain filter combinations, valid values for approvalLevel, or how date filters interact. It merely restates the resource type.

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 'Search for billing item approval levels', specifying a specific verb and resource. It further explains that these are multi-level approval records tied to time entries, which distinguishes it from sibling search tools like autotask_search_time_entries or autotask_search_billing_items.

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 implies usage context (tiered approval workflows) but does not explicitly state when to use this tool versus alternatives, such as autotask_search_billing_items for item-level data. No guidance on when not to use it or prerequisite conditions.

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