GetDetailsOfElements

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

Annotations already declare readOnlyHint and openWorldHint=false, so safety is covered; the description adds non-obvious behavioral context that unlisted fields are not computed at all and that floorPlanPolygons extraction dominates batch execution time. That is genuine performance information beyond the structured fields.

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 front-loaded sentences: purpose first, then the performance-relevant tip. Only the trailing '(Tapir, Element Commands)' tag is wasted space.

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?

No output schema exists, but the field enum plus the description's explanation of returned fields and the omission default make the return shape inferable. For a read-only lookup tool the coverage is adequate, though it doesn't describe the shape of 'details' itself.

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 only 50%, so the description carries weight, and it does: it explains the semantics of 'fields' as a filter that also suppresses computation, and what happens when omitted (every field returned). The 'elements' parameter is left implicit, which is acceptable given its self-evident name.

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 and resource ('Gets the details of the given elements') and adds scope with 'geometry parameters etc', which separates it from property/classification siblings like GetPropertyValuesOfElements. It doesn't explicitly name any sibling, so it stops short of a 5.

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?

Gives useful in-tool guidance on how to call it (use the optional fields parameter to skip unneeded computation), but offers no when-to-use-this-vs-alternatives routing against the many sibling read tools such as GetAllElements or GetPropertyValuesOfElements. Usage is implied rather than framed.

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