Get HyperExecute Job Sessions

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

With no annotations, the description fully covers behavioral traits: it declares read-only nature, explains how status/search_text filters return errors instead of empty lists, notes that tests without sessions are excluded, and describes cursor-based pagination. This provides complete transparency.

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 long but well-structured with front-loaded purpose and differentiation. It is dense with valuable information, and every sentence adds utility. Minor opportunity to tighten, but overall effective.

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?

Given no output schema, the description thoroughly describes each entry's fields (session/test ID, parent Task ID, scenario name, status, group number, duration, SmartUI). It also covers pagination, error handling, and parameter behavior. The tool is moderately complex and fully covered.

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?

Schema description coverage is 0%, but the description explains all five parameters in detail: job_id (required, same ID as used by related tools), limit (max 20, default 10), cursor (pagination behavior), status (filter), and search_text (filter by scenario name). It compensates fully for the schema gap.

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 session-level execution details for a HyperExecute Job, and explicitly distinguishes from the sibling tool tm.get_hyperExecuteJobScenarios by explaining the difference in how retried tests and failed-to-session tests are handled. This is specific and actionable.

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 clear context on when to use this tool versus alternatives, explicitly comparing with tm.get_hyperExecuteJobScenarios and noting differences. It also explains the input job_id and optional parameters. It lacks an explicit 'when not to use' but the guidance is strong.

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