Download External RFI PDF Export

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, but the description adds substantial behavioral detail: it is explicitly read-only, returns a redirect + JSON object with file/download URL, and discloses failure modes with specific HTTP statuses (401, 403, 404). This goes well beyond the structured 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?

The description is dense but every sentence carries purpose: usage trigger, defaults, prerequisites, response shape, read-only guarantee, error modes, and API endpoint. It is slightly long but not wasteful given the tool's complexity.

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?

Despite having no output schema, the description fully explains what the tool returns (JSON object with generated file or download URL), how errors surface (error payload with HTTP status), required parameters, and defaults. This is complete for a download/read-only tool.

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% with basic 'URL path parameter' descriptions, but the description adds valuable semantics: company_id and project_id default to procore_set_config values when omitted, and external_rfi_id/id must identify existing parent records resolved via list tools. This context is not present in the schema.

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 starts with 'Returns a redirect to download the generated PDF export for a specified External RFI' — a specific verb and resource that clearly distinguishes this download tool from sibling list/show tools. The endpoint path further reinforces the exact operation.

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 when you already know which external RFI PDF export you want and need its full field set' and instructs to resolve IDs with the matching list tool first. This provides clear when-to-use context and a prerequisite step, effectively differentiating from lookup or listing alternatives.

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