erinys_session_start

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

With no annotations, the description must disclose behavior itself, but it only states that a session is started. It leaves unaddressed whether this is a mutation, whether it requires authentication, whether it resets ongoing work, or what side effects may occur. This is a significant omission for a tool that changes state.

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 short sentence, but its brevity results in under-specification rather than efficiency. Essential information about parameters, behavior, and usage context is missing, so the sentence does not earn its place as the sole documentation.

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?

Given that the tool has three parameters, no annotations, and a session-lifecycle context involving sibling tools, the description is far too minimal to be complete. It does not explain what the output schema represents, whether sessions can overlap, or any prerequisites, making it inadequate for reliable invocation.

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?

The schema lists id, project, and directory with no descriptions, and the tool description does not mention any of them. At 0% schema description coverage, the agent has no way to know the expected format, purpose, or defaults of these parameters from the description.

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 names a specific action (start) and resource (session), distinguishing it from siblings like erinys_session_end and erinys_session_summary. However, it does not explain what a session is or what starting one entails, so it is clear but lacking depth.

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 provides no guidance on when to use this tool, what conditions should hold before starting a session, or how it relates to alternatives such as erinys_session_end or erinys_context. It is simply a command with no situational or exclusions context.

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