Astria-Index

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

With no annotations provided, description carries full burden and discloses: ordering behavior (chronological), filtering logic (category tag matching), pagination constraints (default 20, max 100), and empty state handling. Lacks explicit safety declaration (read-only) but implies it via 'Browse' and return value documentation.

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 (purpose, differentiation, usage guidelines, Args, Returns). Every sentence earns its place; examples are specific and front-loaded with the primary action. No redundant or filler text.

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 having an output schema (per context signals), description proactively documents return structure (IDs, content, category, importance, timestamps) and empty list behavior. For a 2-parameter list operation with no annotations, coverage is comprehensive.

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 has 0% description coverage (no parameter descriptions in JSON), but the tool description fully compensates by documenting both parameters in the Args section, including the enum values for category (preference, fact, decision, etc.) and limit constraints (max 100).

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?

Opens with specific verb ('Browse') + resource ('stored memories') + ordering constraint ('most recent first'). Explicitly differentiates from sibling tool `recall` by contrasting chronological vs. semantic search, clearly delineating scope.

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 'Use this when:' section with four concrete scenarios including parameter examples. Explicitly names alternative tool (`recall`) and explains when to use each, satisfying the 'when/when-not' requirement.

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