get_monitor_session_messages

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

With no annotations, the description must carry behavioral disclosure, and it does: default window of newest 100, a 200 maximum, the limit-0-means-default rule, ASC timestamp ordering unless order is supplied, and the offset-based paging semantics. It omits any auth/permission or rate-limit context, but for a read window tool the disclosed defaults and ordering behavior are substantive.

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?

Three tight sentences with the purpose front-loaded and no filler. There is mild redundancy with the schema (limit 0 uses the default, max 200 both appear in the schema), which keeps it from a 5.

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 no output schema and no annotations, the description covers defaults, clamping, ordering, and pagination adequately. It does not clarify how the window is selected relative to the sibling message tools, which is the main remaining gap.

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 description coverage is 100%, so the baseline is 3. The description reinforces the semantics of limit (default/clamp), order (ASC unless supplied), and offset (page into older history), which is useful framing but largely restates what the schema already documents per-parameter.

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 opens with a specific verb+resource: 'Get a window of messages for a session.' It is clear what the tool returns and its scope (a window of messages), which the agent can distinguish from list-style siblings. However, it never names or contrasts with nearby siblings like get_monitor_messages or get_monitor_message, so it falls short of full sibling differentiation.

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 gives one concrete usage instruction ('Use offset to page into older history'), which is genuinely helpful. But it offers no guidance on when to use this tool versus the sibling message retrieval tools (get_monitor_messages, get_monitor_message, get_shared_messages), so the when/when-not dimension is only implied.

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