erinys_context

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only implies a read-only operation via 'get'. It does not explain what 'session context' refers to, whether results are sorted or paginated, or how 'recent' is determined. This is insufficient for a tool that retrieves contextual data.

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, concise sentence with no redundant phrasing. It is front-loaded with the main action and resource, but it is so short that it omits important usage and parameter details, which trades conciseness for completeness.

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 parameters, an output schema, and a long list of siblings, this description is too minimal. It does not explain return values (though output schema exists), parameter meanings, or how this tool relates to others. The tool's niche remains ambiguous.

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%, and the description only implicitly mentions the 'project' parameter. It does not explain 'limit' or 'intended_use' (which has a default of 'context'), leaving two of three parameters semantically opaque. The description fails to compensate for the low schema coverage.

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 'Get recent session context for a project' clearly identifies the verb ('get') and resource ('recent session context for a project'), providing a straightforward purpose. However, it does not differentiate itself from sibling tools like erinys_session_summary or erinys_recall, so it falls short of a 5.

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?

The description gives no guidance on when to use this tool versus alternatives such as erinys_session_summary or erinys_recall. It lacks any context about appropriate use cases, prerequisites, or exclusions.

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