List Session Activities

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is known. The description adds meaningful context about the activity types, return format, and pagination behavior, which goes beyond annotations and helps set expectations.

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 well-structured with a brief main statement, a bulleted list of activity types, an Args section, Returns line, and examples. It is not overly verbose, though the Args section duplicates schema information, slightly reducing conciseness.

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 list tool with four parameters and no output schema, the description covers the essential aspects: what activities are tracked, the return value shape, pagination via pageToken, and example usage. It doesn't address error cases or auth, but is sufficient for typical use.

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 input schema already provides comprehensive descriptions for all four parameters (sessionId, pageSize, pageToken, response_format), so schema coverage is 100%. The description's Args section essentially repeats the schema without adding new semantics, maintaining the baseline score of 3.

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 opens with 'List all activities for a Jules coding session', which clearly identifies the verb (list) and resource (activities for a session). The bulleted list of activity types adds specificity about what is included. It does not explicitly contrast with sibling tools like jules_get_activity, but the plural 'all activities' makes the scope evident.

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 examples 'Monitor session progress: provide sessionId' and 'Get full history: paginate through all activities' give practical guidance on when to use this tool. While it doesn't explicitly mention alternatives, the context of monitoring and history retrieval is clear, and the pagination hint is useful.

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