List Agent Published Sessions

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

The annotations already declare readOnlyHint, openWorldHint, and idempotentHint, establishing this as a safe read operation. The description adds the 'published' qualifier, which narrows the scope, but provides no additional behavioral details such as pagination, ordering, or what 'published' means in this context.

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 with no filler. It is front-loaded with the verb and resource, making it immediately actionable and well-structured.

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 with one parameter and safe annotations, but the description omits clarification of 'published sessions' and any indication of the return format. Given no output schema, the description could be more informative, though the basics are present.

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 fully documents agent_id with a description ('Agent id'), and the schema coverage is 100%. The description's phrase 'for an agent' adds no additional semantic detail beyond the schema, so the baseline of 3 applies.

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 'List' and identifies the resource as 'published sessions for an agent', clearly stating the tool's function. It does not explicitly contrast with sibling tools like 'lyzr_agent_sessions', which could also list sessions, but the scope is narrowed by the 'published' qualifier.

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 is provided on when to use this tool versus alternative session-listing tools such as lyzr_agent_sessions or lyzr_session_history_by_agent. The description only states what the tool does, not when it should be selected.

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