get_element_properties

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

With no annotations provided, the description alone must disclose behavioral traits. It states the tool 'gets' data, implying a read-only operation, but does not mention error handling, permissions, or potential side effects (though none are expected). The description is straightforward but lacks explicit safety guarantees, which would be useful without annotation support.

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, front-loaded sentence containing no redundant or filler content. It conveys the essential function in fewer than twenty words, earning a perfect score for efficiency.

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 an output schema exists (so return values are likely defined there), the description still lacks enough context for an agent to use the tool confidently. It doesn't explain the role of ifc_path, how it relates to the IFC file, or how this tool differs from the sibling extract_ifc_quantities. The tool appears simple, but the missing parameter context and lack of usage alternatives make it incomplete.

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 0% description coverage, so the description must compensate for unclear parameters. It mentions 'GlobalId' (mapping to global_id) but entirely omits ifc_path, leaving its purpose and format unexplained. This is a significant gap since both parameters are required and not self-explanatory from names alone.

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 ('Get'), identifies the resource ('all property sets and quantities'), and specifies the key input ('by its GlobalId'). This clearly distinguishes it from general listing tools like query_ifc_elements or statistics tools, making the purpose immediately obvious.

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 no guidance on when to use this tool versus alternatives such as extract_ifc_quantities or query_ifc_elements. It does not mention prerequisites (e.g., having an IFC file loaded) or exclusions, leaving the agent to infer appropriate usage from the name and schema.

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