get_session_history

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

No annotations provided, so description carries full burden. Describes return format and trend types but omits behavioral details like rate limits, data freshness, or side effects. Adequate for a read-like tool but not comprehensive.

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?

Four sentences, each essential. Front-loaded with purpose, no redundant phrasing. Efficient and easy to parse.

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 only 2 parameters and no output schema, description covers key aspects: returns, parameters, use case, and disclaimer. Could improve by explaining trend values or handling of missing sessions, but sufficiently complete for a tool with low complexity.

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 coverage is 0%, so description must compensate. It adds meaning to 'minutes' (lookback window, default 5, max 60) but does not elaborate on 'session_id' beyond being required. Partially fills the gap.

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?

Clearly states the tool gets state history for a session over time, listing specific returned fields (stress_score, state, heart_rate, trend). Differentiates from siblings like get_human_state by focusing on session 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?

Provides explicit context: minutes parameter controls lookback window with default and max, useful for detecting stress patterns during conversation. Includes disclaimer 'Not a medical device.' However, does not explicitly mention alternative tools or contradictory usage.

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