Show BIM Level

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

Annotations already mark it as read-only and idempotent. The description adds only that it returns a JSON object. Does not disclose error behavior, authentication, or rate limits. With strong annotation coverage, the description adds minimal behavioral context beyond what's already provided.

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?

Four sentences, each serving a clear purpose: purpose, usage, return type, required params and API context. Efficient and well-structured with no redundant information.

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 the core task of retrieving a single BIM Level with required parameters. However, could mention the effect of the 'view' parameter on the response structure or note that page/per_page are for pagination. For a simple read tool, mostly complete but lacks final polish.

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 has 100% description coverage for all 5 parameters. The description only restates that 'id, project_id' are required, which is already in the schema. No additional meaning or context is added beyond what the schema provides.

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?

Clearly states it returns a single BIM Level item. Distinguishes from siblings like create, delete, list via verb 'Return' and the phrase 'single BIM Level item'. Mentions API endpoint and required parameters, leaving no ambiguity.

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?

Explicitly says 'Use this to fetch the full details of a specific BIM records by its identifier.' This implies it's for retrieving one item, but lacks explicit contrast with alternatives like list_bim_levels for multiple items. However, the context of siblings makes the use case clear.

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