Retrieve detailed information for a specific billing item using its ID. Access billing item details directly from Autotask PSA.
Get detailed information for a specific billing item by ID
| Name | Required | Description | Default |
|---|---|---|---|
| billingItemId | Yes | The billing item ID to retrieve |
Changes observed during successful MCP inspections.
v2.18.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. Description only says 'detailed information' but does not disclose what fields are returned, if it modifies state, or any authentication/rate limit details. Minimal behavioral disclosure.
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?
Single sentence, no unnecessary words. Front-loaded with verb and resource. 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?
Tool is simple with one parameter and no output schema. Description conveys basic purpose but lacks details on returned data or error handling. Adequate for a straightforward retrieval, but incomplete for an agent to fully understand behavior.
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 descriptions cover 100% of parameters. The description adds 'detailed information' which is vague and does not significantly enhance the schema's definition of billingItemId. Baseline 3 is appropriate.
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 verb 'Get', resource 'billing item', and method 'by ID'. It distinguishes from autotask_search_billing_items (which searches/list) by implying a single specific item retrieval.
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 vs alternatives like autotask_search_billing_items. The description does not mention prerequisites or scenarios where this tool is preferred.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.