Import issues from BCF

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false. The description adds real context beyond that: it runs without dialogs, commits as a single undo step, and matches referenced elements via IFC GlobalId. It does not mention error behavior on failed matches, but the safety/mutation profile is well covered.

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?

Three tight sentences: what it imports, how it behaves on execution, and what it returns. No filler, and the output contract is front-loaded at the end where the agent needs it.

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?

With no output schema, the description supplies the return shape ({imported, issues: [...] in get_issues format}), so an agent knows exactly what it gets back. Combined with the undo-step and dialogs-free behavior notes, nothing critical for correct invocation 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?

Schema coverage is 75%, so the schema documents most parameters. The description only enriches `path` with accepted BCF file extensions and version; undoName, openIssuePalette, and alignBySurveyPoint semantics come entirely from the schema, not the 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?

States a specific verb (imports) and resource (BCF issues/topics/comments/referenced elements) with format scope (.bcfzip/.bcf, BCF 2.x) and target (Issue Manager). It is easily distinguished from export_bcf and get_issues in the sibling list.

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 implies the use case (pulling BCF issues into Archicad) but never states when to prefer it over export_bcf or how it relates to existing issues. No prerequisites or exclusions are given, so usage is only implied.

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