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

Annotations already mark the operation as read-only and idempotent, so the bar for additional disclosure is lower. The description adds meaningful behavior beyond the annotations by noting that details are passed to the product gateway and that supported gateways independently verify provider payment before reporting paid state. This helps the agent understand the external verification behavior without contradicting the annotations.

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 compact at two sentences with no filler, and the second sentence adds genuinely useful behavioral context. The only structural weakness is the slight mismatch between the tool name's 'get' action and the description's 'Pass ... back' phrasing, which could confuse on first read.

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?

With no output schema, the description should explain return semantics, but it only hints at 'reporting paid state' without defining other possible statuses, errors, or what happens when payment is not verified. It also omits practical details like what to put in the details object and how to choose among the service_id enum values. An agent would likely need further information to invoke this reliably.

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 0%, and the details parameter is an arbitrary object with no property descriptions, so the description must compensate. It only says 'product-specific tracking details' and never explains which fields belong in details or how service_id maps to specific gateways/products. This is too thin to construct the request correctly.

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 title and tool name clearly supply the verb+resource: get verified Evercraft order status. The description adds the mechanism ('Pass product-specific tracking details back to the product gateway'), and the scope is distinct from siblings like get_evercraft_offers or prepare_evercraft_checkout. It is not perfectly explicit that the tool returns the status, but the intent is recoverable.

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 have product-specific tracking details and need gateway-verified payment/order status, but it never explicitly names alternatives or states when NOT to use this tool. Sibling tools are not referenced, so the guidance is contextual rather than exclusionary.

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