Erinys Recall

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

With no annotations, the description carries the full burden, yet it only implies recency ordering. It does not say whether results are session-scoped, project-scoped, capped, or ordered, nor whether the call has side effects. An output schema exists, so return values need not be explained, but the retrieval behavior remains opaque.

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 single sentence is efficient and front-loaded with the verb, but its brevity comes from under-specification rather than tight editing; nothing about the phrasing earns its place on its own.

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?

For a tool with three undocumented parameters, no annotations, and a crowded sibling namespace, one generic sentence is not enough. The output schema covers return values, but the input contract and selection criteria are left entirely to inference.

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 description coverage is 0% across three parameters, so the description must compensate and does not. It never explains 'limit', the 'project' scope filter, or the cryptic 'intended_use' parameter whose default is 'context' — a value an agent has no way to interpret.

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 verb 'recall' and object 'recent observations' give a rough sense of purpose, but 'for context' is vague and the description never distinguishes this from siblings like erinys_get, erinys_search, erinys_context, or erinys_timeline, which all plausibly retrieve stored items.

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?

There is no indication of when to call this versus erinys_search or erinys_context, no prerequisites, and no statement about what 'recent' means in scope. The agent must infer usage entirely from the terse sentence.

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