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

With no annotations, the description carries the full transparency burden. It adds useful behavior beyond the basic transformation by mentioning deduplication and a pay-per-use cost. However, it does not disclose input format requirements, rate limits, failure modes, or whether the operation has any side effects, so the transparency is partial.

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 a single information-dense sentence. It front-loads the purpose, enumerates the output fields, and appends pricing in brackets. There is no fluff or repetition, and every part earns its place.

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?

With no annotations and no output schema, the description alone must fully equip an agent to invoke the tool. It fails to explain how the 'input' parameter should be provided or formatted, and while it lists output fields, it gives no structure or return contract. An agent would likely know what the tool does but not exactly how to call it correctly.

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?

The schema has one generic parameter described only as 'pipeline input', so the schema itself conveys almost no meaning. The description partially compensates by indicating the input should be business card photos, but it does not specify whether that is a URL, file path, base64, or multipart content. Since schema coverage is 100% but the schema description is unhelpful, a baseline-3 score is appropriate.

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 uses a specific verb and resource: it turns business card photos into clean, deduplicated contact records. The list of extracted fields (name, title, company, phones, emails, address, socials) makes the tool's scope precise and clearly distinguishes it from OCR siblings focused on invoices, receipts, tables, or handwriting.

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 use case is clearly implied: when you have business card photos and need structured contact records, this is the tool. It does not explicitly name alternatives or exclusion criteria, but the business-card-specific wording provides enough context to route an agent away from general OCR or document-specific OCR tools.

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