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 carries full burden for behavioral disclosure. It only states the tool 'searches' but does not reveal important traits like read-only nature, pagination behavior, authentication needs, or potential side effects. The description adds minimal transparency beyond the implicit search action.

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 with the purpose front-loaded. No redundant or filler content. Every word contributes to understanding.

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?

Lacks details on return format (no output schema), pagination defaults, or how parameters combine. While the purpose is clear, a more complete description would mention that results include approval level, approver, timestamps, etc. Given the tool has 7 parameters and zero required, the description is minimally adequate.

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 86%, so most parameters are already documented with filters (e.g., timeEntryId, approvalLevel). The description adds no additional meaning beyond what the schema provides, making it adequate but not compensatory for the 14% gap. Baseline score of 3 is appropriate.

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 tool searches for billing item approval levels, which are multi-level approval records for Autotask time entries. This verb+resource combination is specific and distinguishes it from sibling tools like autotask_search_billing_items which searches billing items generally.

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 such as autotask_search_billing_items or autotask_search_time_entries. The description lacks exclusions, prerequisites, or context about the search scope.

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