Show BIM File Extraction

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds only that it returns a JSON object, which is minimal. No additional behavioral traits (e.g., authorization, rate limits) are disclosed. No contradiction with annotations.

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 4 sentences, each adding unique value: purpose, usage, output, and API details. No redundant or unnecessary sentences. Front-loaded with the core action.

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 covers the basic purpose and required parameters, but lacks explanation of optional params (page, per_page) given they appear in the schema for a single-item endpoint. No output schema means the description could compensate by describing the output structure, but it only says 'JSON object'. Somewhat incomplete for a tool with 4 parameters.

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 schema already documents all 4 parameters. The description only repeats required params (id, project_id) without adding meaning beyond what the schema provides. The page and per_page params are not explained in context; for a single-item retrieval, pagination seems irrelevant, creating a minor gap.

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 single BIM File Extraction with full details by identifier. The title and description together distinguish it from the sibling tool 'list_bim_file_extractions', which returns multiple records.

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 explicitly says 'Use this to fetch the full details of a specific BIM records' and lists required parameters, implying it's for individual retrieval. However, it does not mention alternatives or when not to use it. The sibling list tool is not referenced.

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