list_bindings

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

With no annotations, the description carries full burden and does an excellent job. It discloses the exact output categories (datasets, field names, page types, repeater children behavior) and even notes that IDs are auto-minted when attaching bindings. This is rich, specific behavioral context beyond a simple 'lists bindings' statement.

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 long sentence with several clauses, but every part contributes useful information (examples, page types, usage). It is front-loaded with the main purpose and then provides specifics. It could be split into multiple sentences for better readability, which is why it doesn't get a 5.

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 parameters, no output schema, and no annotations, the description is remarkably complete. It covers the purpose, the information returned, examples of field names, page type requirements, repeater behavior, and how to use the results (auto-minted IDs). There are no obvious gaps for an agent to select and invoke this tool 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?

The input schema has zero parameters, so there is nothing to explain. Baseline for zero params is 4. The description adds contextual value by explaining what the output contains and how to use it, though it doesn't need to discuss parameter semantics.

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 a specific action ('List every dynamic-data BINDING target') and identifies the resource (datasets, field names, page types, repeater children). It goes beyond a generic list by enumerating examples and usage context, effectively distinguishing it from other listing tools like list_global_sources or list_elements.

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 clear context for when to use the tool: when you need to discover dynamic-data binding targets. It also gives an explicit downstream usage ('Attach via new_element opts.bindings') with an example, but it does not explicitly mention alternatives or when not to use this tool, which is a minor gap.

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