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

The readOnlyHint=true annotation is consistent with a verification operation. Beyond annotations, the description discloses the full ten-step pipeline (signature, expiry, DID match, segment authorization, spend limit, currency, daily cap, trust score, delegation chain, traveler binding), which is genuinely useful behavioral context an agent cannot get from structured fields. It stops short of saying whether a failed verification raises an error or returns a negative verdict.

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?

Front-loaded with the core action and the pipeline list, which is the highest-value content. The trailing Args block is redundant given 100% schema coverage and a third of the text could be cut, but overall the description is short and skimmable.

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?

Six required parameters are all documented, an output schema exists so return values needn't be explained, and the ten-check pipeline conveys the depth of what happens. The remaining gap is outcome semantics — success/failure reporting and whether any state is written despite the read-only hint.

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%, and the Args block in the description is essentially a verbatim restatement of the schema descriptions (agent_did, merchant, currency examples included). It adds no meaning beyond the schema — notably, `segment` is not actually constrained to an enum despite the four enumerated values, which the description could have clarified as an allowed-value contract.

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 and resource — "Verify a travel booking against a TravelAgentCredential" — and enumerates the ten checks performed, which makes it unmistakable against siblings like mt_travel_issue_vc and mt_travel_info. An agent can pick this tool without opening the schema.

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 only implied: an agent infers this is a pre-booking credential check, but the description never says when to call it versus mt_shopping_verify, moltguard_credential_verify, or the travel issue/info siblings. No preconditions, no statement of what a caller should do on failure, and no exclusions.

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