Download Remote Artifacts

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

Annotations declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, implying some state change (likely writing files to disk), but the description's 'Return artifact paths' conveys a pure read and never discloses any side effect. It also omits session-lifecycle context (must the session be closed first?) and error behavior. The only added value is the 'finished session' precondition.

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?

A single short, front-loaded sentence with no filler. It is efficient, though its brevity contributes to the ambiguity noted elsewhere.

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 one-parameter remote-session tool with no output schema, the description omits what 'recorded' artifacts are, how a session becomes 'finished', and where the paths originate. Given the dense cluster of remote-execution siblings, richer lifecycle context is needed for correct invocation.

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?

The single parameter session_id has 0% schema description coverage. The description's 'for a finished session' loosely ties the parameter to a session, but adds no format, source, or lookup guidance for the id, so it does not 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 gives a verb ('Return') and a resource ('artifact paths'), but 'Return artifact paths' directly conflicts with the name and title 'Download Remote Artifacts', leaving the agent unsure whether the tool fetches file content or merely enumerates paths. It also does not distinguish this from sibling remote-session tools such as close_remote_session or poll_remote_run.

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 explicit guidance on when to call this versus alternatives, nor any mention of prerequisites beyond the loose hint 'for a finished session'. The agent is left to infer that a remote session must exist and be complete before use.

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