memdata_session_start

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

No annotations provided, so description carries full burden. It does not disclose side effects (e.g., whether it mutates state, creates a new session, or is idempotent). Only mentions what it returns, not behavioral characteristics like safety or mutability.

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?

Description is a single sentence with emoji for visual emphasis. It is front-loaded with the call-to-action and efficiently lists what the tool returns. Every part adds value without redundancy.

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 no output schema and no parameters, the description adequately lists return items (identity, handoff, activity, memory stats). It is mostly complete, though lacks details on whether multiple calls are safe or if it establishes a session context.

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?

No parameters exist, so schema coverage is 100% by default. The description does not need to add parameter meaning, and the baseline of 4 applies as no additional info is required.

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?

Description clearly states to call first at session start, lists return items (identity, last handoff, recent activity, memory stats), and distinguishes from sibling tools like memdata_session_end. The verb 'CALL THIS FIRST' and resource 'session' are specific and actionable.

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 says 'CALL THIS FIRST at the start of every session,' providing clear context for when to use. Does not mention when not to use or alternative tools, but the directive is strong and unambiguous.

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