Get 8DX Wallet Session

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

With no annotations provided, the description carries the full burden. It discloses the conditional behavior ('if one is set') and the session type (non-custodial), but does not specify the return format or error behavior when no session exists. This is acceptable for a simple getter but lacks richer detail.

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, front-loaded sentence with no redundant words. Every word adds value, making it highly concise 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?

Given the tool's simplicity (no parameters, no output schema, no annotations), the description adequately covers its purpose and conditional nature. It could optionally mention what is returned when no session is set, but overall it is complete enough for a trivial getter.

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 tool has zero parameters, and the schema is empty. The baseline score for 0-parameter tools is 4, and the description correctly implies no inputs are required, so it adds appropriate meaning without needing further parameter explanation.

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 the tool returns the current local non-custodial wallet session, using the specific verb 'Returns' and a well-defined resource. The qualifiers 'local' and 'non-custodial' help distinguish it from sibling tools like eightdx_walletconnect_get_session, making the purpose unambiguous.

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 when to use this tool (to get the local wallet session) but provides no explicit guidance on when not to use it or how it compares to alternatives such as eightdx_walletconnect_get_session. The 'local non-custodial' wording offers context, but no direct exclusions or alternative references are given.

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