find_latest_session_file

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

The description discloses key behavioral details: the selection is deterministic and based on filename ordering, not semantic relevance. This is crucial for understanding how the tool behaves and prevents misinterpretation. No annotations are present, so the description carries this responsibility well.

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 that convey all essential information without any filler. The structure is efficient, front-loading the core purpose and then providing necessary usage guidance.

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 gives sufficient context for the tool's role: it identifies the file type, explains how the latest is determined, and tells the agent the next step (pass to load_context_files). It also warns against a common misuse (relying on snippets), making the tool's place in the overall workflow clear.

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 only parameter `project_path` is fully documented in the schema with acceptable formats (absolute path, owner/repo, or full URL). The description itself does not add extra semantic detail about the parameter, but with 100% schema coverage it does not need to. Baseline score of 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: to deterministically find the most recent .context/sessions/*.md file. It specifies the resource type and the exact operation, leaving no ambiguity about what the tool does.

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 usage instructions: pass the returned path to `load_context_files` and warns against relying on the tool's snippets alone. This tells the agent exactly how to use the result and what to avoid, which is ideal guidance.

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