Api chat questionnaire runs object retrieve

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered structurally. The description adds only the 'Experimental' tag, with no information on permissions, what happens to a run in prefill state, or response shape.

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?

One short front-loaded sentence with no padding, but it is under-specified rather than concise. Nothing is wasted, yet little is delivered.

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 retrieve tool with an undocumented required parameter and no output schema, the description should explain what a 'run' is and what is returned. Neither is present, leaving the agent to guess from the endpoint name alone.

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 0% and the single required 'id' parameter is undocumented in both schema and description. The description does not say what the id identifies or what format it takes, so it fails to compensate for the coverage gap.

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 'Experimental: questionnaire prefill runs' names the domain but never states the verb or that it fetches a single run by id. With siblings like questionnaire_runs_retrieve, _object_retrieve and _list all present, an agent cannot distinguish this tool from them without reading the schema.

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?

There is no indication of when to use this versus questionnaire_runs_retrieve or _object_retrieve, nor any precondition. The only hint is the 'Experimental' label, which suggests caution but does not guide selection.

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