autotask_search_tasks

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

No annotations provided, so description must compensate. It mentions default page size (25) and pagination behavior, which is useful. However, it doesn't disclose read-only nature or any side effects. Since the tool is a search, it's likely safe, but not explicitly 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?

Description is short and front-loaded with key purpose. Two sentences, no fluff. Could be slightly improved by adding a sentence about when to use or additional context, but it's efficient.

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 6 parameters, description adequately covers core behavior and pagination. However, it lacks guidance on search behavior (exact match, wildcards?) and return format. For a search tool, more detail on result structure would help.

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?

Input schema has 100% description coverage, so description adds no new parameter meaning. The description only notes pagination defaults which are already in schema. Baseline 3 is appropriate as schema does the job.

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?

Description clearly states the tool searches for tasks in Autotask and mentions pagination details. It effectively communicates the core function, though it could be more specific about filtering capabilities beyond defaults.

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 basic context (search tasks) but does not differentiate from sibling search tools (e.g., autotask_search_projects, autotask_search_tickets) or specify when to use this tool over others. No alternative tools or when-not-to-use guidance given.

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