GetValues

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

With no annotations, the description carries the burden. It does add useful behavioral signals: it is a batched read and the phrase 'snapshot' implies a non-mutating view of runtime state. However, it does not disclose timeout/partial-failure behavior, whether values are returned as a map, or how this differs from evaluating expressions (RuntimeEval).

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 short sentences, each earning its place: the core action, the default no-names behavior, and the intended use case. It is front-loaded and contains no filler.

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 read-only tool with zero required parameters and fully documented schema, this is largely complete. The main omissions are the return shape (no output schema) and explicit routing against GetValue/ListValues, but the basics needed to select and invoke the tool correctly are present.

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 description coverage is 100%, so the schema already documents all three parameters. The description's 'if no names provided, returns all values' restates the names parameter's schema description rather than adding new semantic detail. Baseline 3 is appropriate.

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 action ('Get multiple values'), a clear resource ('Observable runtime'), and a distinguishing batch dimension ('at once') that separates it from the singular GetValue sibling. The all-values-when-no-names behavior and snapshot framing further pin down its purpose.

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 suggests a use case ('getting a snapshot of the runtime state') but never explicitly instructs when to choose this over GetValue, ListValues, RuntimeEval, or other siblings. The batch/plural semantics imply the distinction, but that is left to inference rather than stated.

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