sit_with

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

Annotations already declare readOnlyHint=false and destructiveHint=false. The description adds the concept of 'open' and 'live longer', but does not elaborate on behavioral details, such as whether it modifies session state or creates records. The addition is valuable but not extensive.

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?

Two sentences plus 'Free' are highly concise and front-loaded. Every sentence earns its place with essential information and no 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?

With 7 parameters and no output schema, the description is too brief. It doesn't explain invocation effects (e.g., on session state, database entries) or how parameters like 'days' and 'revisit_in_hours' interact. More details are needed for a complete understanding.

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 100%, so the schema already explains all parameters. The tool description adds no further parameter-specific meaning, e.g., it doesn't clarify 'ritual_strip' or 'revisit_in_hours' behavior. Baseline 3 is appropriate.

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 clearly states the tool's purpose: opening a question for long-term contemplation. The verb 'open a question' is specific and differentiates from quick-solving approaches, effectively distinguishing from sibling tools like 'quick_session' or 'reflect'.

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 context for when to use: 'when the agent is not trying to solve quickly, but to remain in relationship with a question over time.' While it doesn't name alternative tools or state when not to use, the guidance is clear and sufficient.

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