List XRC process sessions

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

The description states 'Read-only', implying no side effects, but this is expected for a list tool. With no annotations provided, the description fails to disclose any additional behavioral traits like authentication needs, rate limits, or error handling.

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 short sentence, making it concise. However, it lacks structure and does not front-load critical information such as required parameters or output format.

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?

With 7 parameters, no schema descriptions, no annotations, and no output schema, the description is severely incomplete. It does not explain filtering options, return values, or any constraints, making it inadequate for an AI agent to use 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?

Given 0% schema description coverage, the description should explain the parameters. It only mentions 'XRC-729 OSTC id/hash', which hints at ostcId and ostcHash but does not clarify other parameters like xrc729Address, owner, windowHours, page, or limit. The schema names alone are insufficient.

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 is a 'Read-only list of sessions' and specifies the association with an 'XRC-729 OSTC id/hash', which indicates the tool's purpose. However, it does not explicitly differentiate it from sibling tools like list_xdala_sessions, leaving some ambiguity.

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 no guidance on when to use this tool versus alternatives such as list_xdala_sessions or list_xdala_session_ids. There is no mention of prerequisites, filters, or situations to avoid.

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