h3yun_session_info

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

With no annotations provided, the description carries the behavioral burden. It clearly indicates a read-like 'Return' operation, but it does not mention prerequisites such as being signed in, possible error behavior, or whether any state is modified. The zero-parameter schema and 'Return' wording imply a safe read, though more explicit disclosure would be stronger.

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?

One short sentence states both the purpose and the exact return content without filler. The key information is front-loaded and easy to parse.

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 zero-parameter tool with an output schema, the description is nearly complete: it names the two pieces of information returned and the session context. It could add a note about requiring an established session or how it relates to h3yun_login, but the output schema likely covers return-value details.

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 zero parameters and 100% schema coverage, so there is no parameter ambiguity. A baseline of 4 applies for a zero-parameter tool, and the description appropriately adds no unnecessary parameter detail.

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 clear verb ('Return') and names a specific resource (signed-in user and current engine/tenant). This uniquely identifies what the tool does among siblings like h3yun_login, h3yun_list_apps, and h3yun_get_record, so an agent can distinguish it without opening schemas.

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 implies this tool is used to fetch session context, but it gives no explicit guidance about when to use it versus alternatives or whether any precondition such as logging in first is required. There are no stated exclusions or routing hints to other tools.

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