humanitix_get_order

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

With no annotations, the description carries the disclosure burden. It usefully states the default return shape ('trimmed order by default') and the raw override, which is genuine behavioral context. It does not state read-only safety, auth requirements, error behavior for a missing order, or anything about the override_location side effect.

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?

Two tightly written sentences with zero waste; the core operation is front-loaded and the default/override behavior follows immediately.

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 single-fetch tool with no output schema and no annotations, the description conveys the key variable in the response (trimmed vs raw full payload), which is exactly what an agent needs to choose the right call. It is only slightly short of complete, leaving auth and error handling unaddressed.

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 description coverage is 100%, so all four parameters including raw, event_id, order_id, and override_location are already documented in the schema. The description restates the raw flag's trimmed-vs-full behavior but adds no format, constraint, or default detail beyond the schema, so the 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?

States a specific verb ('Fetch') and resource ('a single order'), scoped by event and order identifiers. It implicitly distinguishes itself from the sibling humanitix_list_orders by emphasizing 'single', but never names an alternative explicitly.

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?

Usage is implied by 'single order' versus the list sibling, but there is no explicit when-to-use/when-not guidance and no mention of prerequisites such as required permissions or when to prefer the list endpoint.

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