list_consumer_sessions

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so safety is covered. The description adds useful behavioral context: cross-agent scope and most-recent ordering. It does not describe what fields the returned sessions contain or pagination behavior, but this is moderate added value given the annotations.

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?

Two compact sentences with no filler. The first sentence front-loads the core behavior and qualifiers; the second sentence adds the comparison to get_consumer_profile, which is directly useful for tool selection.

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-only list tool, the description plus schema and annotations are sufficient for correct invocation. The main gap is that with no output schema, the agent gets no hint about the shape of the returned sessions, and there is no explicit differentiation from list_agent_sessions.

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 parameters limit, offset, and consumer_key are already fully documented. The description reinforces 'consumidor específico' as the consumer_key role but adds no new parameter-level semantics.

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 the action ('Lista'), the resource ('sessões de um consumidor específico'), and key qualifiers ('cross-agent, ordenadas por mais recentes'). It also distinguishes itself from get_consumer_profile by contrasting sessions with aggregate counters.

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 explicitly mentions when this tool complements get_consumer_profile, telling the agent that get_consumer_profile only returns aggregate counters while this tool returns actual sessions. However, it does not mention alternative session-list tools like list_agent_sessions or state explicit exclusions.

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