autotask_search_expense_reports

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

Without any annotations, the description carries the full burden of behavioral disclosure. It fails to mention that this is a read-only operation, does not explain pagination behavior (e.g., default page size, max limit), and does not describe what data is returned. The schema captures some constraints, but the description adds no behavioral context.

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 a single sentence, which is concise, but it is too brief to be informative. It lacks structured details that could aid an AI agent. While front-loaded, it does not earn its place due to missing essential context.

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 that there is no output schema, the description should explain what the tool returns. It does not mention that expense reports are the result set, nor does it elaborate on pagination or filter behavior. The description is far from complete for guiding proper invocation.

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 100%, so baseline is 3. The description adds 'optional filters', which is already implied by the schema's 'required: []' and the parameter descriptions. No extra meaning is provided beyond what the schema already conveys.

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 expense reports', which is a specific verb+resource pair. It distinguishes this tool from other search tools (e.g., autotask_search_companies) by targeting expense reports specifically.

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 no guidance on when to use this tool versus other search tools. It does not mention alternatives, exclusions, or prerequisites. The phrase 'with optional filters' is too vague to serve as meaningful usage guidance.

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