Locate And Load Session

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

With no annotations, the description carries the full behavioral disclosure burden, and it does well by adding concrete traits: 100% local search, zero LLM tokens, and a condensed payload with specific contents (objective, recent exchanges, files touched, next step). It does not discuss side effects or failure modes, but the operation reads as non-mutating and the output is well specified.

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 dense sentences with no filler, no repetition of schema fields, and the core action plus output are front-loaded. Every clause earns its place.

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?

The description, combined with a fully documented input schema and an output schema, gives an agent enough to invoke the tool correctly. It could be more complete by explicitly routing to sibling tools or noting edge cases, but nothing essential to calling the tool is missing.

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%, and the schema already documents query, detail, and harness with clear meanings and defaults. The description adds no parameter-level detail beyond the schema, which is acceptable given the high coverage.

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 states a specific verb (locate), a specific resource (a session from another harness), and a concrete deliverable (a condensed ready-to-resume payload). It is clearly distinct from siblings like list_sessions, save_active_session, and refresh_index, which handle browsing, persisting, and indexing rather than retrieval for resumption.

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 phrase 'ready-to-resume payload' and 'from another harness' implies the intended use case, and the '100% local search, zero LLM tokens' note signals a lightweight retrieval context. However, it never explicitly names alternatives or states when not to use this tool, such as pointing to list_sessions for browsing.

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