Metis — Generate Handoff Brief Tool

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

With no annotations, description details what is captured and where it writes, and that it returns the brief. No hidden side effects disclosed, but sufficient for a generation tool.

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?

Three well-structured sentences: purpose, details, usage guidance. No wasted words.

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?

Describes captured data and output, but missing explanation of session_id parameter. Output schema exists but parameter gap hurts completeness.

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 sole parameter session_id is optional with default '' but the description does not explain its purpose or effect. Schema coverage is 0%, so description fails to add meaning.

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 it generates a portable session handoff brief, listing specific captured data and output location. This distinguishes it from siblings like add_journal_entry or save_session_summary.

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 states when to use: before session end, /clear, or device switch. Does not mention when to avoid or alternatives, but context is clear.

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