jules_session_info

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

With no annotations provided, description must fully disclose behavior. It only says 'Get current session configuration and authentication status', implying a read operation, but does not clarify side effects, auth requirements, or what 'session configuration' entails. Lacks detail for a tool with no annotation support.

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?

Single sentence, front-loaded with purpose, zero waste. Ideal length for a simple read tool.

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 zero-parameter tool with no output schema, the description sufficiently conveys the tool's output. Could be slightly more specific about what 'session configuration' includes, but adequate for its simplicity.

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?

No parameters exist, so schema coverage is 100% (trivially). Description does not need to add parameter meaning. Baseline 4 applies as no additional semantics are required but also not provided.

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?

Description clearly identifies the tool's purpose with specific verb ('Get') and resource ('current session configuration and authentication status'). It distinguishes itself from sibling tools that deal with code analysis, task management, cookies, etc.

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?

No guidance on when to use this tool versus alternatives. No mention of context, prerequisites, or exclusions. The description just states the function without usage direction.

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