autotask_get_ticket_charge

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

The description provides minimal behavioral information beyond the basic operation. Given no annotations, it should disclose what happens if the charge ID does not exist (e.g., returns null vs error), whether the operation is read-only, and any permission requirements. It only states 'Get', leaving important behavior undocumented.

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 very short and to the point, with no unnecessary words. It is front-loaded with the verb and key information. However, it could include a bit more context (e.g., result format) without sacrificing brevity.

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 simplicity of the tool (one parameter, no output schema), the description is minimally complete. However, it lacks contextual completeness regarding usage with sibling tools and behavioral guarantees. A more complete description would mention when to use it and what to expect.

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 schema covers 100% of parameters with adequate descriptions. The tool description adds no extra semantic meaning beyond what the schema already provides (e.g., 'by ID' is redundant since the parameter is named 'chargeId'). Therefore, the description meets the baseline but does not enhance understanding.

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 the action is 'Get' and the resource is 'a specific ticket charge by ID'. It is concise and directly conveys the function, but does not differentiate from sibling tools like autotask_search_ticket_charges which could also retrieve charges.

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 is provided on when to use this tool vs alternatives. For example, it does not specify that this tool is for retrieving a single charge by ID, while autotask_search_ticket_charges is for querying multiple charges. This omission could lead to incorrect tool selection.

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