Get Aionis Guide

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

Annotations are absent, so the description carries full burden. It only says 'Return' (implying a read), but provides no information about side effects, return format, errors, or data handling. The qualifier about MCP renderer is technical but not behaviorally transparent.

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 terse sentence, which is concise but overly sparse. It uses jargon without unpacking, and while there is no waste, the lack of essential content makes it ineffective.

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 nested object parameters, no output schema, and no annotations, the description is severely incomplete. It fails to explain what the request should contain, what the response looks like, or how this guide fits into the broader Aionis toolset.

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 coverage is 0%, and the description does not mention parameters at all. The two parameters ('request' and 'context_options') are left completely unexplained, and the nested object structure is undocumented.

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 states a specific action ('Return') and a resource ('canonical SDK Agent context'), but the resource is vague and the qualifier 'without an independent MCP renderer' does not clarify what the context is. It distinguishes little from sibling tools like 'rehydrate' or 'remember'.

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?

No guidance is provided about when to use this tool. There is no mention of prerequisites, alternatives, or exclusions, leaving the agent without any indication of how this relates to session management siblings.

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