osint_isbn_validator

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

Goes beyond readOnlyHint=true and destructiveHint=false annotations by detailing pure local arithmetic, no network call, offline-capable, rate-limited, CAPTCHA possibility, and timestamp embedding for non-identical responses. 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?

Well-structured, front-loaded with core function, and each sentence adds value. Slightly long but not wasteful; could be trimmed slightly for conciseness.

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?

Covers purpose, usage guidelines, behavioral traits, output description (per-ISBN results with aggregate statistics), and optional features. Given complexity and existing schema/annotations, description is fully complete for agent invocation.

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 100%, so baseline is 3. Description adds context (e.g., step-by-step math for showCheckDigitCalculation) but mostly reiterates schema info. Adequate but not exceptional.

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 clearly states it validates ISBN-10 and ISBN-13 by recomputing check digits, reporting format, registration group/language, and conversion. It explicitly distinguishes from sibling tools (osint_ean_upc_validator, osint_barcode_scanner, osint_barcode_generator) with clear when-to-use guidance.

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?

Explicitly states 'Use this for book ISBNs' and provides alternatives for general EAN/UPC barcodes. Also clarifies batch acceptance, offline capability, and rate-limiting, giving clear context for appropriate use.

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