get_elements_batch

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

With no annotations, the description provides useful context: it's a query, lists include options and a default, and highlights efficiency. However, the stated default (['entity_label', 'placement']) conflicts with the input schema's default (null), which is misleading. It also does not mention return format or side effects.

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 concise: two sentences, no fluff, and the option list is compactly integrated. Every phrase contributes meaning.

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?

The description covers the core purpose and include options, but omits return value structure, potential limits, and error behavior. The schema-default contradiction further undermines completeness, leaving gaps for an agent to interpret.

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?

Since the schema has zero descriptions, the description adds value by enumerating valid include options and a default, but that default contradicts the schema. It only vaguely references global_ids via 'by GlobalId' and does not explain model_id, leaving those parameters under-specified.

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 clearly states this is a batch query for elements by GlobalId, distinguishing it from singleton queries like get_element_by_id. The mention of include options further specifies the tool's functionality.

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 explicitly notes the tool avoids multiple round-trips for files with 200+ fixtures, giving a clear use case. However, it does not explicitly contrast with alternatives or state when not to use it.

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