autotask_search_time_entries

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

With no annotations, the description carries the full burden. It discloses that results return 25 per page by default, specifies filterable fields, and mentions the API threshold. It does not detail rate limits or authorization requirements, but the disclosed behaviors are sufficient for safe invocation. A score of 4 reflects good transparency given the absence of annotations.

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 three sentences, each carrying essential information: purpose, default page size and filtering capabilities, and a practical usage tip. There is no redundancy or fluff, making it highly efficient and easy to scan.

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 the high schema coverage and lack of output schema, the description provides all necessary context: it explains what the tool does, how to filter, the default page size, and a critical performance consideration (fan-out with date range scoping). It is complete enough for an agent to use effectively.

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 90%, providing a baseline of 3. The description adds value beyond the schema by explaining the 'unapproved' status as 'not yet posted' and by listing the filtering dimensions in a user-friendly way. This extra context justifies a score of 4.

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's purpose: 'Search for time entries in Autotask.' It identifies the specific resource (time entries) and uses a direct verb ('Search'). The tool is distinct from siblings, which are either for creating or searching other entities.

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 clear guidance on when to use the tool, including filtering suggestions and a specific use case for approvalStatus='unapproved'. It also warns about fan-out and recommends scoping by date range to avoid API thresholds. However, it does not explicitly state when not to use the tool or list alternatives, which would have earned a 5.

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