jules_inspect_bash_logs

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read-only operation and specifies what is returned, but it does not state the absence of side effects, failure behavior for invalid session IDs, availability constraints, or any pagination/limits despite saying 'all' commands.

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?

The description is a single sentence with no filler. It front-loads the core action, resource, and output components, making it easy for an agent to quickly parse the tool's purpose.

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 simple one-parameter inspection tool, the description adequately covers the main purpose and return content, especially given that there is no output schema. It falls slightly short of full completeness by omitting edge-case behavior such as empty logs, invalid sessions, or whether results are ordered or paginated.

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 schema covers the single parameter with 100% description coverage, so the description does not need to repeat it. However, the schema only says 'The session ID,' and the tool description adds no clarification about what kind of session ID is expected or how to obtain it, so parameter semantics remain at the baseline.

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 uses a specific verb ('Extract') and clearly identifies the resource: all terminal shell commands executed inside Google's cloud sandbox, along with exit codes and stdout/stderr output. This unambiguously distinguishes it from sibling tools like jules_get_session or jules_list_activities, which deal with different data.

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 gives no explicit guidance on when to use this tool over alternatives, nor any exclusions or prerequisites. An agent must infer from the name and subject matter that it is for bash log inspection; the large sibling list provides no routing help.

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