Show BIM Model Revision

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

Even with readOnlyHint=true, the description adds value by stating 'Read-only — it changes nothing in Procore.' It also discloses failure behavior ('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') and return shape ('Returns a single JSON object').

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. The first sentence states the purpose, followed by usage, return type, safety, error handling, and required parameters. Every sentence contributes meaningful information without redundancy.

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 single-resource read tool with 3 parameters, the description covers purpose, usage, behavior, errors, required parameters, and even the API endpoint. Since there is no output schema, the description's mention of 'Returns a single JSON object' fills that gap. No missing context.

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 baseline is 3. The description adds extra meaning by clarifying that 'id must identify an existing parent record — resolve it with the matching list tool first,' which goes beyond the schema's simple 'bIM Model Revision ID' label. Other parameters are adequately covered by 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 'Return a single BIM Model Revision' with a specific verb and resource. It also distinguishes from siblings by specifying 'Use this when you already know which BIM model revision you want and need its full field set,' implying the list tool is for discovery.

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 explicit when-to-use guidance: 'Use this when you already know which BIM model revision you want and need its full field set.' It also instructs to 'resolve it with the matching list tool first,' offering a clear path for obtaining the required id.

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