Get Observation Item PDF Url

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

Annotations already indicate readOnlyHint, destructiveHint, idempotentHint, openWorldHint. The description adds value by detailing the return type (JSON with file contents or download URL) and the API endpoint, providing additional context beyond annotations. 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?

The description is concise (4 sentences) and front-loaded with the primary purpose. The inclusion of API details (Procore API, endpoint) adds some verbosity but remains structured and clear. Could be slightly more focused without the API reference.

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?

The description explains the return format (JSON with file contents or download URL) and required parameters, but does not clarify how the PDF URL relates to pagination parameters (page, per_page) or what happens when the PDF is not available. The ambiguity between 'file contents' and 'download URL' reduces 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 description coverage is 100%, so the schema already documents all four parameters. The description redundantly mentions required parameters but does not add any new meaning. The page and per_page parameters are not explained in context of PDF retrieval, leaving ambiguity.

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 returns a PDF URL for a specified Observation Item, distinguishes itself from other observation tools (e.g., list, show, create) by focusing on fetching the PDF. It specifies required parameters and the return type (JSON with file contents or download URL).

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?

The description says 'Use this to fetch the full details of a specific Observations by its identifier,' but it lacks explicit guidance on when not to use it (e.g., when a non-PDF representation is needed) and does not mention alternative tools like show_observation_item. Context is implied but not fully explicit.

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