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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds value by disclosing that the view is 'customer-safe' (i.e., filtered/sanitized) and by enumerating the state domains returned, which an agent cannot infer from structured fields. No contradiction with 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?

A single front-loaded sentence that opens with the verb and ends with a scope qualifier. The domain list is slightly dense but each element is informative; 'Read-only' mildly duplicates the readOnlyHint annotation.

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?

No output schema exists, so the description correctly compensates by enumerating the returned state domains. Combined with annotations covering safety, an agent has enough to invoke it correctly; only error/edge behavior on the token is missing.

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?

With one parameter and 0% schema description coverage, the description must carry the semantics. 'Using its tracking token' identifies the token as the hunt identifier, which is helpful, but it adds nothing about format, the 12-240 character constraints, or how an invalid/expired token behaves.

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 (Retrieve) and a precisely enumerated resource (customer-safe Part Passport, sourcing-lane, evidence, payment, fulfillment and solution state) scoped to a FindMyPart hunt. It is clearly distinguishable from get_part_hunt_offers and prepare_part_hunt_checkout by naming the aggregate state domains, though it never explicitly contrasts itself with those siblings.

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: call this with a hunting tracking token to read current state. There is no guidance on when to prefer it over get_part_hunt_offers, free_part_triage, or get_findmypart_capabilities, and no preconditions or exclusions are stated.

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