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

With no annotations, the description carries the full burden of behavioral disclosure. It discloses the 3-stage pipeline, the return values, the paid $0.10 fee, and the accepted payment rails. It does not mention failure modes, image format requirements, or latency, but it is substantially transparent.

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 well-structured and front-loaded with the core purpose, followed by pipeline details, outputs, pricing, and usage. Some details such as the audit reference and exact chain addresses are slightly extraneous, but the organization remains readable and purposeful.

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 the absence of an output schema, the description adequately describes the return values, payment cost, and settlement rails. The main gap is the unexplained `game` parameter, but the essential information an agent needs to select and invoke this tool correctly is present.

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 input schema provides no property descriptions. While the description implies that `image_url` is a trading card image and that the grade relates to PSA/Beckett, it never explains the `game` parameter, acceptable values, or image URL constraints. The description only partially compensates for the missing schema documentation.

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 opens with a specific verb and resource: 'AI-grade a trading card image using a 3-stage pipeline.' It also clearly states the outputs, namely PSA/Beckett-calibrated subgrades and an overall condition score. However, it does not explicitly distinguish itself from the similarly named sibling tool `grade_or_not`.

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 includes an explicit 'Use this when' statement: a user has a card image and wants to know what grade it would receive from PSA or Beckett. This gives a clear triggering context, though it does not provide when-not-to-use guidance or name alternatives.

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