get_hitl

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

No annotations are provided, so the description carries the burden. 'Get details' implies a read-only operation, but it does not mention error conditions (e.g., 404 if not found), authentication needs, or the exact structure of the returned details. This is minimally transparent for a simple retrieval tool.

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, front-loaded sentence with no filler. Every word earns its place, making it appropriately concise.

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 one-parameter get tool, the description is adequate but not rich. It lacks guidance on alternatives, response format (no output schema), and any edge-case behavior. It meets the minimum viable bar but does not go beyond.

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 describes escalation_id fully ('The ID of the escalation to retrieve'), and schema coverage is 100%. The description adds no extra meaning beyond the schema, such as value format or default behavior, so baseline 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 states a specific verb ('Get') and resource ('details of a specific HITL escalation'). The word 'specific' distinguishes it from sibling list_hitls, and it is clearly distinct from mutation tools like create_hitl, approve_hitl, modify_hitl, and reject_hitl.

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 details for a single escalation, but it does not explicitly state when to prefer this over list_hitls or provide any context about prerequisites (e.g., needing an escalation_id). No alternative tools are mentioned or excluded.

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