Get Sessions

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

The readOnlyHint and idempotentHint annotations already establish that this operation is safe and has no side effects. The description adds context that sessions record the agent, execution status, and timing information, which helps set expectations for the output. It does not mention any additional behavioral traits beyond that, such as pagination or rate limits, so it adds some but not extensive value beyond the annotations.

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 two sentences: the first states the purpose with a direct verb and resource, and the second provides useful context about what a session is. No filler, no repetition, and the most important information is front-loaded.

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?

This is a simple read-only list tool with one optional parameter and an output schema present. The description explains what sessions are and what data they contain, while annotations cover the safety profile. Nothing critical is missing for an agent to use this tool correctly.

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 100% coverage of the single optional parameter 'agent_name', with a clear description: 'Optional agent name used to filter sessions'. The tool description does not add any extra meaning to the parameter, so it relies on the schema, which fully documents it. Baseline 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 opens with 'List agent sessions from Itential Platform,' a specific verb and resource that clearly states the tool's function. It further distinguishes the resource by explaining that sessions are created when agent automations are triggered via endpoint triggers, setting it apart from sibling tools like get_agents and get_jobs.

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 provides implied usage context by defining what a session is, which helps an agent infer when to use this tool versus listing agents or jobs. However, it does not explicitly name alternative tools or specify when not to use this tool, so guidance is only implicit.

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