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

Annotations already establish readOnlyHint, destructiveHint=false, and a closed-world scope, so the safety profile is covered. The description adds only that results are authorization-scoped ('authorized child result links'), which is useful but thin; it says nothing about pagination, truncation, or what happens if the run is incomplete.

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 front-loaded sentence with no filler. It is efficient, though its brevity is partly the reason the usage and behavioral gaps exist.

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 single-required-parameter read tool with no output schema, the description roughly covers the return shape (metadata plus child result links) and the safety profile comes from annotations. Missing are run-state caveats and how this relates to sibling retrieval tools, so it is adequate but not 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?

With a single parameter at 100% schema description coverage, the schema fully documents run_id, so the baseline of 3 applies. The description adds no format, sourcing, or validity detail beyond the schema (e.g., where to obtain a run_id).

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 (read) and resource (workflow result metadata plus authorized child result links), which is clearer than a bare 'get results'. It does not, however, distinguish itself from near-siblings like get_result or get_workflow_run, leaving ambiguity about which retrieval tool applies.

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 guidance on when to use this tool versus get_result, get_workflow_run, or read_job_file, and no mention of prerequisites such as run authorization. The agent must infer the selection from the tool name alone.

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