Astria-Index

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

With no annotations provided, the description carries the full disclosure burden. It successfully documents the 48-hour auto-expiration of completed sessions, the empty-list behavior when no sessions exist, and the specific fields returned (IDs, descriptions, status, timestamps). Minor gap: does not mention ordering (e.g., by recency) or potential rate limits.

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?

Well-structured with clear sections for purpose, usage scenarios (bullet points), and return values. The 'Use this when' section is slightly verbose with three bullet points, but each provides distinct context (timing, status-checking, decision-making). Front-loaded with the core action statement.

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?

Despite the existence of an output schema (not shown), the description provides valuable semantic context about the returned data structure and session lifecycle. Combined with comprehensive usage guidelines and zero parameters requiring documentation, the description is complete for this tool's complexity level.

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?

Input schema contains zero parameters. Per scoring rules, 0 params warrants a baseline score of 4. The description correctly implies the parameterless invocation pattern with `my_sessions()` in the usage example, adding no confusion.

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 opens with the specific verb 'List' and resource 'active sessions', explicitly stating the scope (sessions 'you can resume'). It clearly distinguishes from siblings by referencing `resume_session` as the follow-up action and implying contrast with `start_session` for new work.

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?

Provides explicit temporal guidance ('at the start of every new conversation', 'first thing to call') and decision-making criteria ('Deciding whether to start a new session or resume'). It explicitly names the sibling alternative (`resume_session`) for the continuation workflow, leaving no ambiguity about tool selection.

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