archicad_list_elements

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered externally. The description still adds useful behavior context by disclosing the compact field set returned and the relative cost versus GetDetailsOfElements. It omits any mention of the default limit/truncation behavior, which is a minor gap.

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?

Two short sentences with the resource and return shape front-loaded and the sibling comparison immediately after. Nothing is redundant and every clause adds 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?

For a read-only list tool with full schema coverage, no output schema, and annotations covering safety, the description is nearly complete: it says what comes back and when to use it. The remaining gap is the lack of differentiation from the several other element-listing siblings, which an agent would have to resolve elsewhere.

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 description coverage is 100%, including limit, elements, elementType, and selectedOnly, so the schema carries parameter meaning. The description adds no per-parameter syntax or format detail beyond what the schema already states, which is the expected baseline when the schema does the heavy lifting.

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 (list) and resource (elements) and enumerates the returned fields (guid, type, ID, story name, layer name). It also names a sibling, GetDetailsOfElements, and contrasts itself with it, so an agent can distinguish the two without opening either schema.

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?

"use it to find elements before acting on them" gives clear when-to-use context, and "Much smaller than GetDetailsOfElements" routes the agent away from the heavier sibling. It does not, however, address the other list-like siblings in the family (GetAllElements, FilterElements, GetElementsByType), so the routing guidance is incomplete.

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