get_session_logs

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

Despite no annotations, the description reveals it returns concatenated text, most recent first, and implies read-only behavior. It adds value by describing the output format and ordering beyond the schema.

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?

The description is concise with three clear sections: purpose, Args, Returns. Every sentence adds value and is front-loaded with the primary action.

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?

For a simple read tool with one parameter, the description covers what logs contain, how they are returned (text, ordered), and the parameter's behavior. The presence of an output schema further reduces the burden.

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 description adds crucial meaning to the 'limit' parameter: 'Number of recent logs to return (default 3, max 5).' Since schema description coverage is 0%, this fully compensates by providing the purpose and bounds.

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 'Read recent daily session logs — summaries of previous coaching conversations,' using a specific verb and resource. It distinguishes itself from sibling tools like get_archived_session_log by focusing on recent logs.

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?

It provides context 'Provides conversation continuity,' implying when to use. However, it does not explicitly state when not to use or mention alternatives like get_archived_session_log for older logs.

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