Astria-Index

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

With no annotations provided, the description carries full burden: discloses 48-hour session expiration, permanent persistence of promoted items, requires active (not completed) session, and specifies error conditions (empty takeaways, non-existent session).

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 Args/Returns sections and front-loaded purpose. Length is justified by zero schema coverage, though slightly verbose relative to the minimal structured data available.

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?

Comprehensive for a 2-parameter tool: explains return value semantics (count promoted), error states, sibling relationships, and the critical business logic of temporary vs permanent storage despite output schema being present.

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?

Despite 0% schema description coverage, the Args section fully compensates: session_id includes format example ('s001') and state constraint ('active'), while key_takeaways explains content requirements ('Be specific and include context').

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 a specific verb+resource ('Save the most important things from a session as permanent memories') and clearly distinguishes from siblings by explaining the 48-hour expiration constraint and the relationship to end_session.

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?

Explicitly states 'Use this when:' followed by three concrete scenarios, including the specific temporal constraint 'Before calling `end_session`' and a complete code example showing exact parameter usage.

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