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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that the retrieved state covers 'payment/fulfillment/solution', providing useful context about what data is returned. However, it does not disclose error behavior, rate limits, or token validation, so the added value beyond annotations is moderate.

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 concise, with the main action and resource in the first sentence, followed by a short 'Read-only.' note. The second sentence is redundant with annotations but not verbose. The structure is front-loaded and readable, though the 'Read-only.' could be considered unnecessary.

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 simple read tool with one parameter and no output schema, the description gives a high-level indication of what is returned ('payment/fulfillment/solution state') but lacks details about the response structure or possible error conditions. Given the lack of an output schema, more specificity about the return content would improve completeness, but it is minimally sufficient.

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 coverage is 0%, so the description must compensate for the undocumented parameter. It clarifies that the 'tracking_token' identifies a specific hunt and is used to retrieve its current state, which adds meaning beyond the schema's type and length constraints. It does not detail token format or validation, but the semantic role is clear.

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 states a specific verb ('Retrieve') and a resource ('current payment/fulfillment/solution state for a FindMyPart hunt'), which is distinct from siblings like get_part_hunt_offers (offers) and prepare_part_hunt_checkout (checkout). The purpose is unambiguous and not a tautology of the name.

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 provides no explicit guidance on when to use this tool versus alternatives. It does not name sibling tools or conditions for selection, leaving the agent to infer usage from the name alone. The mention of 'using its tracking token' implies a prerequisite but not a usage context.

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