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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds useful context beyond that: active-profile scoping, newest-first ordering, and the exact returned fields, which matters because there is no output schema. It does not explain limit/pagination behavior.

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?

A single compact sentence, front-loaded with scope and ordering, followed by the return fields. The field list is dense but justified because no output schema exists.

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?

Because there is no output schema, the field enumeration is valuable and makes return values clear. The main gap is the undocumented limit parameter, which affects how the agent should call the tool.

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 is one parameter, limit, with a default of 10, but schema description coverage is 0% and the description never mentions it. It therefore does not compensate for the missing parameter documentation, leaving the agent to guess the meaning and bounds of limit.

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 that it returns recent conversations for the active profile, newest first, and enumerates the fields. It is distinguishable from single-session siblings like dialogue_result, though it does not explicitly name alternatives.

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 implies use for viewing recent conversation history but gives no explicit when-to-use guidance, prerequisites, or comparison to dialogue_result or dialogue_state. The agent must infer when this is the right tool.

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