get_pdf_report_link

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

No annotations provided, so description fully shoulders transparency. It discloses tool is idempotent: 'Pure URL construction — no scan triggered, no network call.' Describes output format: 'Returns a JSON object with `pdfUrl`' and fetch behavior: 'fetching the URL itself returns `application/pdf` of the latest scan results.' No contradictions.

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?

Highly concise: three sentences cover purpose, behavior, output, usage guidelines, alternatives, and auth. Front-loaded with key action and outcome. Every sentence adds value with zero 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?

Given tool simplicity (1 param, no output schema, no nested objects), description fully covers what it does, how it works, what it returns, when to use, and what not to use. No missing critical details 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?

Only one parameter 'domain' with schema description 'Domain name, e.g. example.com'. Schema coverage is 100%, so baseline 3. Description adds no additional semantics beyond the schema's example; no further constraints or formatting details are provided.

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 clearly states verb 'Build' and resource 'direct PDF report endpoint URL for a domain.' It specifies 'Pure URL construction — no scan triggered, no network call from this tool.' Explicitly distinguishes from siblings like get_badge_link and create_report_snapshot, ensuring no confusion.

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 when to use: 'Use for downloadable shareable reports.' Provides clear alternatives: 'use get_badge_link for an embeddable SVG status badge instead, or create_report_snapshot for an immutable hashed evidence URL.' Also notes 'No auth.'

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