Get File By Its UUID

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

The description goes well beyond the annotations. It explicitly states 'Read-only — it changes nothing in Procore' (consistent with readOnlyHint), and adds significant context: the return format ('Returns a single JSON object describing the file'), the behavior for local vs remote storage, and detailed error scenarios ('Failures come back as an error payload carrying the HTTP status — commonly 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve'). This gives the agent a clear model of what happens on success and failure.

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 a single paragraph with 7 sentences, each conveying necessary information without fluff. It is front-loaded with the core action, then covers usage, prerequisites, return type, read-only nature, error handling, and API reference. While a bit dense, every sentence earns its place, and the structure is logical. It could be slightly more concise by merging some clauses, but overall it is efficient.

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?

For a simple get-by-UUID tool with one parameter and no output schema, the description is remarkably complete. It explains what the tool does, when to use it, the prerequisite for the uuid, the return type, the fact that it is read-only, and typical failure modes. The presence of good annotations (readOnlyHint, idempotentHint, destructiveHint) reduces the burden, but the description still fills remaining gaps such as error handling and how to get the uuid. Nothing significant is missing.

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?

The schema already describes uuid as 'URL path parameter — uUID of the file' (100% coverage). The description adds valuable semantics: 'uuid must identify an existing parent record' and instructs to 'resolve it with the matching list tool first.' This tells the agent what the parameter represents and how to obtain a valid value, which is beyond the schema's basic type/format description.

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 clearlystates the tool's function: 'Get binary file content (from the local disk) or redirect to the File service (on remote storage).' It specifies the resource (file by UUID) and the action (get/retrieve). It also distinguishes from sibling list tools by noting 'Use this when you already know which file you want and need its full field set.'

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 provides a clear condition for use: 'Use this when you already know which file you want and need its full field set.' It also gives a prerequisite: 'uuid must identify an existing parent record — resolve it with the matching list tool first.' It does not explicitly name an alternative tool for listing, but the phrase 'matching list tool first' implies that listing is done elsewhere. This is strong guidance but not a full when-not/alternatives statement.

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