get_historical_sessions

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

Annotations are absent, so the description must disclose behavior. It only says 'Historical sessions... with optional filters,' which is a summary rather than behavioral details. No mention of return format, potential data volume, pagination, timezone handling, or any limitations.

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 one short phrase with no wasted words, achieving a high level of conciseness. However, it is not a complete sentence and reads more like a label, which slightly reduces structure quality.

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 the tool has 12 parameters and no output schema, the description is insufficient. It does not indicate what fields are returned, whether results are paginated, how filters interact with the time period, or what the output structure looks like. The schema covers parameters but not return semantics.

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 input schema provides thorough descriptions for all 12 parameters (100% coverage), so the description does not need to add parameter details. The schema already explains period vs. startDate/endDate, filters, and defaults, making the description's omission acceptable.

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 identifies the tool as providing historical sessions for an app over a period, with the term 'historical' distinguishing it from live session tools. However, it lacks an explicit verb like 'retrieves' or 'lists,' making it a noun phrase rather than a full action-oriented sentence.

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?

No guidance is given on when to use this tool versus alternatives such as get_live_sessions or get_session_details. It only states what it does, not when to prefer it or when to use other tools.

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