list_elements

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

With no annotations, the description carries the burden and does so well: it discloses read-only file-mode behavior, the need to close Word documents, loud refusal of inapplicable filters, cached field results with refresh instructions, and per-type reporting details such as broken reference-field pairs.

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 long, but every segment adds needed information for a polymorphic enumeration tool. The type-by-type highlights are dense and somewhat run-on, yet the overall structure is front-loaded with purpose and return shape before details.

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 tool with no annotations, three parameters, and no schema-level descriptions, the description covers purpose, supported types, filter behavior, output shape, operational constraints, caching, refresh paths, and related tools. Nothing essential is missing for an agent to call it correctly.

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 descriptions are 0%, so the description must explain parameters; it enumerates every valid type value, gives the filter shape with 'range' and 'name' semantics, and explains applicability. file_path is only implied via 'file mode,' and range start/end units are not spelled out, so a small semantic gap remains.

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 opens with a specific verb and resource: 'Enumerate any collection in one call,' followed by an explicit enumeration of supported element types. It also distinguishes itself from reading individual content by noting returned ids/indices are the handles that set_/delete_/manage_ tools take, and it redirects string lookup to find_text.

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?

It gives clear operational context: 'list then act' before mutations, 'Read-only, file mode; close documents open in Word first,' and 'To locate a string, find_text.' It doesn't explicitly differentiate from every sibling such as get_outline or get_table, but it makes the primary enumeration workflow and one key alternative explicit.

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