jules_get_media_artifacts

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It scopes what artifacts are returned, but it does not disclose whether the operation is read-only, what the output format is (e.g., file paths, URLs, binary data), or any side effects. This is a significant gap for a tool with zero annotation coverage.

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 sentence that is front-loaded with the action and resource, with no filler. Every word contributes meaning, including the examples that clarify the artifact types.

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 tool has a simple signature (one required parameter) and no output schema, so the description should explain what the caller receives. It says 'extract' but does not clarify whether the result is a list, files, or inline content. Given the lack of output schema and annotations, the description is not fully complete for an agent to confidently invoke it.

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 100%, and the only parameter session_id has a description in the schema, so the baseline is 3. The tool description does not add extra meaning about how session_id is used beyond implying it identifies a Jules session. That is adequate but not additive.

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 names a specific verb ('Extract') and a clear resource ('visual media artifacts'), with concrete examples (screenshots, UI renderings, test failure images). This distinguishes it from sibling tools like jules_get_session or jules_get_patch, so an agent can tell what it does without ambiguity.

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 implies usage context: use it when you need visual artifacts generated in the sandbox. However, it does not explicitly state when to use versus alternatives, nor does it mention any conditions or exclusions. The context is clear but not explicit.

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