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

Annotations declare readOnlyHint=true, and the description adds valuable behavioral detail: returns exact/near/not_found with edit distance, canonical URL, and sha256 fingerprint. It also communicates the integrity motivation ('honesty-by-construction'), enriching the agent's understanding beyond the annotation.

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?

Two sentences, front-loaded with the core purpose ('Provenance check'), followed by return specifics and a rationale. No filler or redundancy.

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?

Tool is simple; annotations cover read-only nature, schema covers parameters 100%, and the description explains return values and intended usage. No output schema is present, but the description sufficiently communicates what the agent will receive.

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 covers both parameters with thorough descriptions (quote min length, id default behavior), so the description does not need to add much. The description references 'quoted passage' consistently but adds no new semantic detail beyond the schema's clear 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?

Description opens with 'Provenance check: verify that a quoted passage actually appears in a post on erikbethke.com' – a specific verb and resource that clearly distinguishes it from sibling tools like search_blog_posts or get_blog_post.

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 instructs 'Use this BEFORE attributing a quote to Erik', giving a clear when-to-use directive. While no alternative tool is named, the intended context is unambiguous and exclusionary (not for general searching).

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