session_end

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

With no annotations, description should fully disclose behavioral traits like side effects, reversibility, or permissions. It mentions summary generation and working memory promotion but omits whether session state is destroyed, if operation is idempotent, or any required permissions.

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 concise sentences with front-loaded main action and efficient sibling differentiation, containing no superfluous information.

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 lifecycle-ending tool with 2 parameters and no output schema, description explains core purpose and sibling differentiation but lacks return behavior, idempotency, and post-operation state. Adequate but not comprehensive.

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 coverage is 100% with descriptions for both parameters. Description adds no additional meaning beyond what schema provides, meeting baseline expectation.

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 the verb 'End' and resource 'agent session via AgentMemoryManager', with specific actions like summary generation and working memory promotion. It also distinguishes from sibling tool 'end_session' by noting it handles the full session lifecycle vs failure distillation.

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 direct comparison with sibling 'end_session' for failure distillation, aiding agent in tool selection. Lacks explicit when-not-to-use or prerequisites, but the contrast is clear and actionable.

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