Get dynamic options

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety is covered; the description's 'Read-only' repeats that rather than adding to it. It does add value with the disclosure that results come back as `options` label/value pairs or, for field pickers, `fields` with types and allowed values — useful behavioral shape even though an output schema exists. The 'fails later on the user's real data' note is genuine context an agent would otherwise lack.

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?

Three tight sentences, front-loaded with purpose then the when-to-use rationale, with no filler. Minor waste in restating 'Read-only' when the annotations already say so.

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 four-parameter, nested-object tool with a full output schema, the description supplies what the structured fields cannot: why the call matters and what failure it prevents. It leaves credential acquisition to the schema's `credentialId` note and the check_setup pointer, which is acceptable, so nothing critical is missing.

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 100%, so the baseline would be 3; the description earns an extra point by illustrating the loader families in prose (tabs, bases and typed fields, questions, calendars), which helps the agent pick the right enum value and understand why `params` varies per loader. It does not name the enum members or map them to required params, leaving that to the schema.

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 gives a concrete verb and resource ('Ask a connected service which values really exist') and then enumerates real instantiations: spreadsheet tabs, Airtable tables and typed fields, Typeform questions, Google calendars. No sibling tool does this — the neighbors are workflow/run/credential management — so an agent can identify it immediately.

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 states the usage condition explicitly ('Use it while configuring a node') and explains the failure mode of not using it ('a guessed tab or field deploys fine and only fails later on the user's real data'), which is a strong motivating rationale. It stops short of naming a competing tool or a when-not-to-use case, and there is no direct alternative to point at.

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