export_session_context

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

No annotations exist, so description must disclose behavioral traits. It mentions aggregation and saving to clipboard/ledger but does not explain if the operation is idempotent, what happens to previous context, permission requirements, rate limits, or side effects.

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?

Single sentence with front-loaded action ('SAVE context') and concise enumeration of aggregated elements. Slightly improved structure could separate purpose from details, but overall no waste.

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 annotations, the description lacks detail on return values, error handling, behavior when parameters are omitted, and impact on shared resources. For a tool that modifies state ('SAVE'), completeness is insufficient.

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%; both parameters have clear schema descriptions. The tool description rephrases 'handoff_message' and 'cloud_sync' but adds no new meaning beyond the schema's own descriptions.

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 action 'SAVE context' and specifies what is aggregated (project metadata, tree, diffs, mental model) and where it goes (clipboard and ledger). This distinguishes from sibling bootstrap_session_context which likely initializes context.

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 implies usage for exporting context but provides no explicit guidance on when to use vs. the sibling tool, no when-not-to-use scenarios, and no prerequisites or alternatives.

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