list_job_sessions

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

Discloses output fields and warns about untrusted data, but does not explicitly state it is read-only or mention authentication requirements. Since no annotations are provided, the description partially covers behavioral traits.

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 concise, front-loads the purpose, and includes a warning and usage hint without unnecessary words. Two sentences and one warning are efficient.

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 tool with one parameter and no output schema, the description covers output fields, ordering, and how to use the results. However, it omits explanation of the 'limit' parameter, which is a minor gap.

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 has a single 'limit' parameter, but the description does not mention it or its effect on output. With 0% schema coverage, the description should compensate by explaining how the parameter works, but it does not.

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 clearly states it lists conversations (job sessions) with providers, ordered newest first, and distinguishes from list_my_jobs by explaining how to use that tool to see jobs related to a specific session.

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?

Provides a specific use case (use list_my_jobs with session_id) and a warning about untrusted data, but does not explicitly state when not to use this tool or compare with siblings like list_conversations.

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