Get variables

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

The description adds a non-obvious server-side limitation ($top unsupported) and explains that variables persist across iFlow executions, giving context beyond the readOnlyHint annotation. It does not address response format or pagination details, but the annotation already covers safe read behavior.

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?

Two short sentences with the core purpose first and the caveat second. No filler or redundancy; every clause adds information.

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 is adequate for a read-only list operation and includes the meaningful $top caveat, but it omits any explanation of the optional query parameters and does not describe the return shape. Without an output schema, a bit more parameter context would make this complete.

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?

None of the four parameters (skip, filter, select, orderby) are described in the description, and schema description coverage is 0%. The $top note does not explain any listed parameter, so the agent gets no semantic help for these OData query options.

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?

Clearly states it lists runtime variables and defines them as state maintained between iFlow executions. This verb-resource pair distinguishes it from parameter- or artifact-focused siblings, though it does not explicitly name an alternative.

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?

Provides no guidance on when to use this tool over siblings like get_string_parameters or get_secure_parameters. It states only what it does and a server-side limitation, with no selection criteria or exclusions.

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