autotask_search_projects

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

No annotations are provided, placing full burden on the description. It discloses pagination (25 per page, use page parameter) but lacks details on read-only nature, authentication requirements, rate limits, or potential side effects. For a search tool, important behavioral context is missing.

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 no redundancy: first sentence states purpose, second provides key pagination behavior. Every word 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?

Given no output schema, the description should indicate what fields are returned in results, but it does not. It also omits that no parameters are required, leaving the agent uncertain if a searchTerm is needed. Essential context for correct invocation is missing.

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 83%, so baseline is 3. The description adds value by noting default page size and hinting at pagination with 'Use page parameter for more results,' but does not detail each parameter's purpose beyond what the schema already provides.

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 explicitly states 'Search for projects in Autotask' with a specific verb and resource, clearly distinguishing it from sibling tools like autotask_search_companies or autotask_create_project.

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 implies usage for searching projects but does not provide explicit guidance on when to use this tool versus alternatives, such as autotask_get_project_note for specific notes or autotask_list_phases for phases. No when-not-to-use instructions are given.

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