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

Annotations indicate readOnlyHint=false, destructiveHint=false. The description adds behavioral steps (permission checks, warnings) beyond annotations. However, it does not detail side effects like notifications or state changes, so slight gap.

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?

Four front-loaded sentences, each serving a distinct purpose: purpose, permission requirement, prerequisite tool call, and handling blocked access. No wasted words.

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 6 parameters with zero schema descriptions and no output schema, the description covers high-level usage steps but omits parameter details (e.g., what 'reasonKey' or 'note' means). Provides enough for basic usage but not full understanding.

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 description does not explain any parameter meanings, valid values, or constraints beyond the bare names. The requestType enum is visible in schema but description adds no context. Minimal value.

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 ('Create a refund or cancellation customer ticket') and the specific resource ('physical product order'). It distinguishes itself from sibling tools by specifying the ticket type and business context.

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?

Explicitly provides when-to-use guidance: check business permissions, FREE businesses cannot use, call check_business_tool_access before collecting inputs, show grace-period warning and resubscribe link, never proceed when blocked. This is exemplary.

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