list_bindings

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

readOnlyHint=true already declares the safety profile, so the description adds value by disclosing the content shape: datasets, exact field-name syntax, page-type requirements, and repeater per-item binding. It omits pagination/volume characteristics, but for a finite list of binding targets that gap is minor.

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?

Front-loads the purpose in the first clause before elaborating on datasets, field syntax, and the new_element handoff. Dense with parentheticals but each element earns its place; no filler sentences.

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?

With no output schema, the description usefully describes what is returned (datasets, field names, page types, repeater binding patterns) and how to use the result. Complete enough for a zero-param discovery tool, though it could note the payload shape more concretely.

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?

Zero parameters, so the baseline is 4. The description adds no parameter semantics but none are needed; the schema is trivially empty and requires no compensation.

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 a specific resource (every dynamic-data BINDING target), enumerating concrete examples (datasets like product/cart_item/order, field names like 'product::product_price'). No sibling tool covers binding targets, so it is clearly distinguishable.

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 routes the agent through the workflow by naming the consumer: attach via new_element opts.bindings with a concrete example. It doesn't state explicit when-not-to-use conditions, but the usage context is clear and actionable.

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