autotask_search_time_entries

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

Discloses pagination (25 results per page) and API threshold concerns. No annotations, so the description carries the burden. Could mention error behavior or idempotency, but covers key behavioral traits.

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?

Four sentences, each earning its place: purpose, pagination, typical filters, and a performance tip. No redundancy, front-loaded with key 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?

Adequate for a search tool with 10 parameters, no output schema, and no annotations. Covers purpose, pagination, key filters, and API considerations. Could add error handling details, but not required.

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 90%, so baseline is 3. Description adds value by highlighting common filters (approvalStatus, date range) and default page size. Reinforces but does not significantly extend schema info.

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 it searches for time entries in Autotask, a specific verb and resource. It distinguishes from sibling tools like autotask_search_tickets by mentioning time-entry-specific filters (approval status, date range).

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?

Provides explicit guidance: 'Use approvalStatus="unapproved" to find entries not yet posted' and 'scope by date range first to avoid Autotask's API threshold.' Lacks explicit when-not-to-use, but the sibling set makes it clear this is the only time entry search tool.

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