compare_ifc_models

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

With no annotations, the description must carry the transparency burden. It implies a read-only operation via 'report' but does not explicitly disclose side effects, permissions, or performance considerations. The behavioral detail about reporting added/removed/modified elements is helpful but limited.

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 a single, well-structured sentence that is front-loaded with the action and resource. No unnecessary words or repetition.

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?

While the output schema exists (reducing the need to describe returns), the description lacks details on parameter ordering and usage context. The tool is simple, but the lack of parameter documentation and usage alternatives makes it minimally complete.

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?

The schema has zero description coverage (0%) and only two string parameters (ifc_path_v1, ifc_path_v2). The description hints at these being IFC versions but does not clarify their roles (e.g., old vs. new) or expected formats. It fails to compensate for the schema's lack of parameter documentation.

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 uses a specific verb 'Compare' with a clear resource ('two IFC versions') and specifies the output ('added, removed, and modified elements'). This clearly distinguishes it from sibling tools like query_ifc_elements or get_ifc_statistics.

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 provides clear context for when to use the tool (comparing two IFC versions) but does not explicitly mention alternatives or exclusions. However, the context is sufficient to infer its niche relative to siblings.

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