refresh_sessions

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

No annotations are provided, so the description carries the full burden. It discloses the tool's purpose (scanning and indexing) and effect (making sessions searchable), but lacks details on permissions needed, rate limits, whether it's idempotent, or what 'indexing' entails technically. It adds some context but is incomplete for behavioral transparency.

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 sentences, front-loaded with the core action and followed by usage guidance. Every word earns its place—no redundancy or fluff. Efficiently conveys purpose and when to use in minimal text.

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 0 parameters, no annotations, and an output schema (which handles return values), the description is reasonably complete. It explains what the tool does and when to use it, but could improve by adding more behavioral context (e.g., side effects, time to index). The output schema reduces the need for return value details.

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?

There are 0 parameters, and schema description coverage is 100% (empty schema). The description doesn't need to explain parameters, so it meets the baseline of 4 for tools with no parameters, as it can't add value beyond what the schema already provides (none).

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 verb ('Scan for new or updated session files and index them') and resource ('session files'), distinguishing it from siblings like get_session (retrieve one), list_sessions (list existing), and search_sessions (search indexed sessions). It specifies the action of indexing, which siblings don't cover.

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: 'Run this if recent sessions aren't showing up in search results.' This provides a clear trigger condition and implies an alternative (waiting for automatic indexing or using search_sessions without refresh). It differentiates from siblings by addressing indexing lag.

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