jules_result

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

With no annotations, the description carries the behavioral burden. It discloses that this is a retrieval operation and that outputs are only included after completion, but it does not explain behavior for incomplete sessions, such as whether it returns a partial object, errors, or waits for completion.

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 concise sentence with no filler. It front-loads the core action and includes the most important condition ('when completed') efficiently.

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 is simple, has one required parameter, and an output schema exists, so the description does not need to detail return structure. However, it omits guidance on how an agent should handle or detect an incomplete session, and it does not reference how to obtain a valid session_id from sibling tools like jules_start or jules_status.

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 description coverage is 0%, and the description does not explain session_id's format, origin, or relationship to the returned session object. The parameter is simple and self-descriptive, but the description adds little semantic value beyond what the schema already shows.

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 states a specific action and resource: 'Retrieve the full session object, including outputs when completed.' It is clear that this tool returns session data and outputs, which helps distinguish it from status-only or listing tools, though it does not explicitly name a sibling for differentiation.

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 phrase 'when completed' implies the tool should be called after a session finishes, but there is no explicit guidance on when to use this tool versus jules_status, jules_activity, or jules_list_sessions. No alternatives or exclusions are stated.

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