Get Observation Item PDF Url

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

Description contradicts annotations: readOnlyHint=true while description says it records a 'PDF shared' entry in change history and 'treat it as an action rather than a cacheable read.' It also internally contradicts itself by later claiming 'Read-only — it changes nothing in Procore.' This is a serious inconsistency.

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 lengthy and contains redundant or confusing statements (e.g., 'Returns a JSON object containing the generated file or a download URL for the observation item PDF URL'). The contradiction about read-only vs. action further muddies the message. Not well-structured or concise.

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 return type and error scenarios, but the critical contradiction about whether this is read-only vs. has side effects means the agent cannot trust the context. No output schema, so description carries full burden, but the misleading 'read-only' statement severely undermines completeness.

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 clear parameter descriptions. The description adds useful semantics: `id` must identify an existing parent record and should be resolved with the list tool first, going beyond 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 clearly states the tool generates a PDF for a single Observation Item and returns a time-limited download URL. This specific verb+resource combination distinguishes it from sibling tools like show_rfi_in_pdf_format.

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?

Provides context: use when you know which observation item you need, and instructs to resolve `id` via the matching list tool first. It also warms against treating it as a cacheable read. Missing explicit alternatives or exclusions, but adequate.

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