Get Action Inquiry

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that the response includes status and resolution, but it does not describe error handling (e.g., behavior when the inquiry ID is not found) or any permission requirements, leaving important behavioral gaps.

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, concise sentence with no redundant words or filler. It front-loads the core purpose and remains easy to parse.

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?

For a simple get-by-id tool with no output schema, the description adequately states the purpose and hints at the return content (status and resolution). It could be slightly more complete by explicitly noting error behavior or what happens if the inquiry is not found, but overall it meets the needs for tool selection.

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 fully documents the inquiryId parameter with the description 'Action inquiry Id', and the tool description's phrase 'by its Id' reinforces this. Since schema coverage is 100%, the description adds no substantive meaning beyond the schema, so the baseline of 3 applies.

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 uses the specific verb 'Get' and clearly identifies the resource as 'a single action inquiry by its Id', which distinguishes it from sibling tools that list or perform other actions. It also highlights the included fields (status, resolution), clarifying the tool's exact scope.

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 this tool is for retrieving one specific inquiry when the ID is known, but it does not explicitly state when to use it versus alternatives like list_action_inquiries or get_action. No exclusions or alternative recommendations are provided.

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