jules_activity

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

No annotations are provided, so the description carries the disclosure burden. It does state the operation is a read and enumerates the types of content returned, which is useful. However, it does not explain pagination behavior around page_size, ordering, or how missing/invalid sessions are handled; the output schema presumably covers the return shape.

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 focused sentence that front-loads the core purpose and then adds relevant content categories without filler. Every phrase earns its place.

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 presence of an output schema reduces the need to describe return values, and the tool is a relatively simple read operation. Still, usage guidance and parameter semantics are thin, so the description is minimally adequate rather than complete for confident 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?

Schema description coverage is 0%, and the description does not mention session_id or page_size at all. The phrase 'session activities' only faintly implies session_id, while page_size semantics remain entirely unexplained. This is a meaningful gap because there are no structured parameter descriptions to fall back on.

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 ('Read') and a concrete resource ('Jules session activities'), and lists the content categories: plans, messages, and progress. This clearly differentiates it from siblings like jules_list_sessions, jules_status, and jules_result.

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 that the tool is for reading a session's activity feed, but it gives no explicit guidance on when to choose this over siblings like jules_result or jules_status. There are no exclusions or alternative routing cues.

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