autotask_search_projects

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

No annotations provided, so description carries full burden. It discloses pagination behavior (25 results per page, use page parameter). However, it fails to mention that it is read-only, how filters work, or what the response includes. Minimal but not misleading.

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 sentences directly addressing purpose and pagination. No redundant information. Front-loaded with key action. Every sentence earns its place.

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 explanation of return format, filter combinations, or field details. With 6 parameters and no output schema, the description should provide more context about how to use the tool effectively. Relies heavily on schema descriptions.

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?

The description adds meaning to page and pageSize parameters ('Returns 25 results per page by default. Use page parameter for more results.'), which supplements the schema. Other parameters (status, companyID, searchTerm, projectLeadResourceID) are not mentioned, but schema descriptions cover them (83% coverage). The description provides value beyond schema for pagination.

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 projects in Autotask,' which is specific verb+resource. However, it does not differentiate from other sibling search tools like autotask_search_tickets or autotask_search_tasks, which share similar structure.

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 vs alternatives (e.g., autotask_search_tickets for tickets). No prerequisites or context provided beyond basic pagination. Implied usage for searching projects, but no explicit when-to-use or when-not-to-use.

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