List BIM Files

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

Beyond the readOnlyHint annotation, the description states 'Read-only — it changes nothing in Procore,' confirms return format ('Returns a JSON array of BIM files'), explains pagination behavior, and details error handling with specific HTTP statuses (401, 403, 404). This adds substantial behavioral context.

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 well-structured and front-loaded with the core purpose. Each sentence adds value, including usage, return type, read-only note, and error behavior. It is slightly detailed but not verbose, with a logical flow.

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?

There is no output schema, so the description must convey return behavior. It does so by stating it returns a JSON array, pagination details, and error formats. It could mention the fields in the BIM file objects, but the mention of looking up 'the id' implies the id is present, and the schema's view parameter covers the compact view.

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%, so the baseline is 3. The description adds meaning beyond the schema by noting 'page and per_page control pagination and the response reports how many pages remain,' which explains the purpose of these parameters beyond their individual descriptions.

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 opens with 'Lists BIM Files associated with the specified Project,' providing a specific verb and resource. It further distinguishes from sibling tools by stating 'Use this to discover BIM files or to look up the id of one before calling a tool that needs it,' clarifying its role versus show_bim_file, create_bim_file, etc.

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 explains when to use the tool: 'to discover BIM files or to look up the id of one before calling a tool that needs it.' It implies the context but does not explicitly name alternatives like show_bim_file or state when not to use it.

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