autotask_get_expense_report

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

With no annotations provided, the description must fully disclose behavioral traits. It only states the operation (get by ID), implying a read-only action, but lacks details on authentication needs, rate limits, error behavior (e.g., if report not found), or any side effects. This is insufficient for safe usage.

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 of 8 words, front-loading the essential information. Every word is relevant, and there is no redundancy or excess.

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 the low complexity (1 required parameter, no output schema, no nested objects), the description is adequate for a simple retrieval operation. It covers the basic purpose and parameter, though it could optionally mention what data is returned (e.g., expense items).

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 100% with one parameter 'reportId' already described as 'The expense report ID to retrieve'. The description adds no additional meaning beyond the schema. Baseline score of 3 is appropriate as the schema carries the information.

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 'Get a specific expense report by ID' clearly states the action (get) and resource (expense report). It specifies the retrieval method (by ID), distinguishing it from search tools that return multiple results. However, it does not explicitly differentiate from other 'get' tools or sibling search functions.

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives like search_expense_reports or other 'get' tools. No prerequisites or context are given.

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