autotask_get_ticket_charge

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

With no annotations provided, the description must carry the full burden. It correctly indicates a read operation ('Get'), so the agent knows it's non-destructive. However, it does not disclose what happens if the charge ID is invalid (e.g., error handling) or if it returns null vs throws, leaving minor ambiguity.

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 with no superfluous words. It is appropriately sized for a simple retrieval tool, and every word is necessary.

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 tool has 1 required parameter with full schema coverage, no output schema, and is a simple retrieval operation, the description is largely complete. It explains what the tool does and what input it needs. The lack of output description is acceptable without an output schema, as the return value is implied to be a ticket charge object.

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 input schema has 100% coverage with a single 'chargeId' parameter described as 'The ticket charge ID to retrieve'. The description adds no extra meaning beyond the schema, but since schema coverage is high, the baseline is 3. I rate it 4 because the parameter is simple and the combination of schema and description is sufficient.

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 ticket charge by ID' uses a clear verb ('Get') and resource ('ticket charge'), and uniquely identifies the charge by ID. It distinguishes itself from siblings like autotask_search_ticket_charges and autotask_create_ticket_charge, though it doesn't explicitly differentiate.

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 when you need a single charge by ID, but it doesn't explicitly state when not to use it (e.g., for listing charges, use autotask_search_ticket_charges) or mention prerequisites like requiring an existing ticket charge. The sibling list suggests alternative tools for creation and search, but the description itself provides no guidance.

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